From: Junio C Hamano <gitster@pobox•com>
To: Michael G Schwern <schwern@pobox•com>
Cc: git@vger•kernel.org, "Robin H. Johnson" <robbat2@gentoo•org>,
Eric Wong <normalperson@yhbt•net>,
Ben Walton <bwalton@artsci•utoronto.ca>,
Jonathan Nieder <jrnieder@gmail•com>
Subject: Re: git-svn SVN 1.7 fix, take 2
Date: Tue, 24 Jul 2012 14:51:37 -0700 [thread overview]
Message-ID: <7vipdcesk6.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <500F17A3.60307@pobox.com> (Michael G. Schwern's message of "Tue, 24 Jul 2012 14:46:11 -0700")
Michael G Schwern <schwern@pobox•com> writes:
> A big one is "do not blast 10 emails to a mailing list" but I gather that's ok
> here if a submission needs 10 commits to be well expressed and its done via
> git-send-email? And then if patch #3 needs revision I'm to do it in a rebase
> and resend the whole 10 commits? Am I to think of git-send-email less as a
> means of sending patches to a mailing list and more as a git transport mechanism?
Yes, yes and whatever (even though I think send-email is just a
better MUA/MSA when you want to send patches and isn't restricted
for a _git_ transport, I do not think it matters how you look at it).
> I'm trying to bust it up into easier to digest pieces. I came into this cold
> without much knowledge of the problem ("something to do with
> canonicalization") and no knowledge of the code.
Perhaps it is a good idea to lurk and see how others submit their
topics first?
next prev parent reply other threads:[~2012-07-24 21:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 21:46 git-svn SVN 1.7 fix, take 2 Michael G Schwern
2012-07-24 21:51 ` Junio C Hamano [this message]
2012-07-24 23:06 ` Michael G Schwern
2012-07-24 23:12 ` Jonathan Nieder
2012-07-24 22:02 ` Jonathan Nieder
2012-07-24 22:50 ` Michael G Schwern
2012-07-24 23:03 ` Jonathan Nieder
2012-07-24 23:31 ` Jonathan Nieder
2012-07-24 23:45 ` Junio C Hamano
2012-07-25 1:00 ` Michael G Schwern
2012-07-25 4:53 ` Jonathan Nieder
2012-07-25 5:36 ` Michael G Schwern
2012-07-25 7:14 ` Junio C Hamano
2012-07-25 9:53 ` Michael G Schwern
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=7vipdcesk6.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=bwalton@artsci$(echo .)utoronto.ca \
--cc=git@vger$(echo .)kernel.org \
--cc=jrnieder@gmail$(echo .)com \
--cc=normalperson@yhbt$(echo .)net \
--cc=robbat2@gentoo$(echo .)org \
--cc=schwern@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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