From: Junio C Hamano <gitster@pobox.com>
To: rocketraman@fastmail.fm
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] Add feature release instructions to gitworkflows man page
Date: Sun, 29 Mar 2009 23:57:16 -0700 [thread overview]
Message-ID: <7vk567ijlf.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 1238391319-4953-2-git-send-email-rocketraman@fastmail.fm
rocketraman@fastmail.fm writes:
> From: Raman Gupta <raman@rocketraman.com>
>
> Based on a mailing list discussion, add a description of the workflow,
> and associated commands, for creating a feature release.
The same comment applies to the other one, but this commit log message is
really lacking. If you do not bother to summarize the discussion, place a
pointer to the list archive, and more importantly, please describe *why*
this change is desiable.
I am not sure rewinding and rebuilding of 'next', or even having 'next',
is applicable for other projects as a BCP. Other parts (except for the
"branch -f" bit I've already told you about in the other message) looked
good.
Thanks.
next prev parent reply other threads:[~2009-03-30 6:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 5:35 [PATCH 1/2] Add feature release instructions to MaintNotes addendum rocketraman
2009-03-30 5:35 ` [PATCH 2/2] Add feature release instructions to gitworkflows man page rocketraman
2009-03-30 6:57 ` Junio C Hamano [this message]
2009-03-30 17:59 ` Raman Gupta
2009-03-30 18:14 ` Junio C Hamano
2009-03-30 18:40 ` Raman Gupta
2009-04-01 16:15 ` Junio C Hamano
2009-03-30 6:56 ` [PATCH 1/2] Add feature release instructions to MaintNotes addendum Junio C Hamano
2009-03-30 17:57 ` Raman Gupta
-- strict thread matches above, loose matches on Subject: below --
2009-03-26 1:56 rocketraman
2009-03-26 1:56 ` [PATCH 2/2] Add feature release instructions to gitworkflows man page rocketraman
2009-03-26 6:48 ` Junio C Hamano
2009-03-26 14:35 ` Raman Gupta
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=7vk567ijlf.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rocketraman@fastmail.fm \
/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;
as well as URLs for NNTP newsgroup(s).