[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: A couple of Git ideas: new branches, easier changelogs
- To: or-dev@xxxxxxxxxxxxx
- Subject: Re: A couple of Git ideas: new branches, easier changelogs
- From: Gabriel Burt <gabriel.burt@xxxxxxxxx>
- Date: Thu, 4 Mar 2010 21:39:48 -0800
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-dev-outgoing@xxxxxxxx
- Delivered-to: or-dev@xxxxxxxx
- Delivery-date: Fri, 05 Mar 2010 00:40:03 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=BMZzcV+CI284OPbELcfIAVPbSyoFHrL4E75sHtgGuEc=; b=nuMGnDbhVquyIuYIIv3o8z7Rnw5rp339j8ofOC7CiOR33+PAtrV2lz3rNKmR4bsebz 0a22D4LLhw9e2b3EOlhveZFIPQ++tnS12pwnuj97ay4cR25ceiHK98Zx03pII4aXSViI qwuFWb6ROBh2+4CCDk+o750NIAV9x/EhGGS5Y=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=J3I+9S8AwTpb+rVjWuBzyEOkrfxphhHALq+Ha8M7o3r4BU1u6hKW1HEuuW20UQTl6P U4iEVN6Ddnp7HysOboEDSwoI9nNvqHHIs/rVBgIqDVMLVYl9kl/lGon1BN3w4vTfwEZx 26qkYRsztG6dFVTdWyg+oF6Dku6DzPQi2Q1TQ=
- In-reply-to: <e8ac78311003042102o616dc52cpf1773f20cea11abf@xxxxxxxxxxxxxx>
- References: <e8ac78311003042102o616dc52cpf1773f20cea11abf@xxxxxxxxxxxxxx>
- Reply-to: or-dev@xxxxxxxxxxxxx
- Sender: owner-or-dev@xxxxxxxxxxxxx
On Thu, Mar 4, 2010 at 9:02 PM, Nick Mathewson <nickm@xxxxxxxxxxxxx> wrote:
> Here are some options:
> Â D) Like C, except recognizing that some commits don't warrant
> independent changelog entries... so we add a way to annotate commits
> (e.g., with a footer line) to say "This doesn't go in the changelog!"
> or "This goes in the changelog in the new features section!" ÂOnly
> unannotated commits would need to get manually triaged. ÂWe'd want a
> little script to massage the git log into a draft changelog.
This option makes sense to me - though I'm not a tor hacker (yet).
Using the git commit message as the ChangeLog (and writing them to be
succinct and readable) has been wonderful in several projects on which
I work. We tag most of our commits with [topic] at the start of the
first msg line; could maybe use that for the non-ChangeLog-worthy
commits.
Gabriel