From: Tom Prince <tom.prince@ualberta.net>
To: Junio C Hamano <junkio@cox.net>
Cc: "Brown, Len" <len.brown@intel.com>,
Linus Torvalds <torvalds@osdl.org>,
git@vger.kernel.org
Subject: Re: new file leaked onto release branch
Date: Wed, 14 Dec 2005 14:26:12 -0700 [thread overview]
Message-ID: <20051214212612.GA24501@socrates> (raw)
In-Reply-To: <7virtrxv9c.fsf@assigned-by-dhcp.cox.net>
On Wed, Dec 14, 2005 at 12:45:51PM -0800, Junio C Hamano wrote:
>
> I pointed out one anomaly which is the commit should never have
> been created because it was not even a fast forward but already
> up-to-date case, and it was followed up with exchange of a few
> messages between Linus and you.
>
I don't remember any of the details now, but I remember that an old
version of git or cogito would create bogus fast-forward merges, if they
were used without GNU coreutils. The machine it happend on was running
FreeBSD 4.10, but current versions work fine.
Tom
next prev parent reply other threads:[~2005-12-14 21:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 19:20 new file leaked onto release branch Brown, Len
2005-12-14 20:10 ` Linus Torvalds
2005-12-18 7:08 ` Junio C Hamano
2005-12-14 20:45 ` Junio C Hamano
2005-12-14 21:26 ` Tom Prince [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-19 3:21 Brown, Len
2005-12-19 9:16 ` Junio C Hamano
2005-12-14 22:48 Brown, Len
2005-12-14 23:34 ` Johannes Schindelin
2005-12-15 0:37 ` Junio C Hamano
2005-12-15 1:29 ` Johannes Schindelin
2005-12-14 22:06 Brown, Len
2005-12-14 22:16 ` Junio C Hamano
2005-12-14 21:51 Brown, Len
2005-12-14 21:31 Brown, Len
2005-12-14 18:27 Brown, Len
2005-12-14 9:58 Brown, Len
2005-12-14 9:41 Brown, Len
2005-12-14 7:57 Len Brown
2005-12-14 8:37 ` Junio C Hamano
2005-12-14 9:39 ` Junio C Hamano
2005-12-14 16:26 ` Linus Torvalds
2005-12-14 16:53 ` Linus Torvalds
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=20051214212612.GA24501@socrates \
--to=tom.prince@ualberta.net \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=len.brown@intel.com \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.