From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] 0.4 release plans and git comments
Date: Tue, 22 Jan 2008 22:42:15 -0800 [thread overview]
Message-ID: <1201070427-sup-2914@south> (raw)
In-Reply-To: <1200987860-sup-9887@south>
Reformatted excerpts from William Morgan's message of 2008-01-22:
> There've been enough bug fixes and other changes that I'm going to try
> to push 0.4 out the door over the next few days. I'll try and give a
> report of what features are in and which are still percolating in
> next.
Everything that was applied to next is now in master. 0.4 release
imminent!
> The upshot is that, if you submit a patches, it should typically be
> cut against master, not against next. (I'll update the wiki to reflect
> this.) Then I can merge topics into next just as before, but there's
> no false dependence between features introduced by Git.
I've updated the wiki with better Git instructions.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-01-23 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 8:04 William Morgan
2008-01-23 6:42 ` William Morgan [this message]
2008-01-23 6:57 ` Richard Heycock
2008-01-23 18:18 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1201070427-sup-2914@south \
--to=wmorgan-sup@masanjin.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox