From: Jerome Lovy <t2a2e9z8ncbs9qg@brefemail.com>
To: git@vger.kernel.org
Subject: Rationale for the "Never commit to the right side of a Pull line" rule
Date: Thu, 26 Oct 2006 18:47:43 +0200 [thread overview]
Message-ID: <ehqp1u$j4$1@sea.gmane.org> (raw)
Hi,
Could someone please point me to / give me the rationale for the "Never
commit to the right side of a Pull line" rule ?
I found the rule in the second Note of the git-fetch man-page (eg
http://www.kernel.org/pub/software/scm/git/docs/git-fetch.html).
It's been taken over in _bold letters_ by X.Org/freedesktop.org in their
"UsingGit" document (http://freedesktop.org/wiki/UsingGit).
In both places though, I don't see any explanation, but rather a
commandment ;-) . Am I missing the ovious ?
My candid thoughts: to me the practice recommended here seems
subjectively "cleaner" indeed, but is it objectively better or even
essential? Why?
TIA
Jérôme
next reply other threads:[~2006-10-26 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 16:47 Jerome Lovy [this message]
2006-10-26 17:11 ` Rationale for the "Never commit to the right side of a Pull line" rule Linus Torvalds
2006-10-26 17:26 ` Karl Hasselström
2006-10-26 17:30 ` Jakub Narebski
2006-10-27 8:56 ` Luben Tuikov
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='ehqp1u$j4$1@sea.gmane.org' \
--to=t2a2e9z8ncbs9qg@brefemail.com \
--cc=git@vger.kernel.org \
/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).