From: Linus Torvalds <torvalds@osdl.org>
To: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>
Cc: Andreas Ericsson <ae@op5.se>, Eric Wong <normalperson@yhbt.net>,
Martin Langhoff <martin.langhoff@gmail.com>,
git@vger.kernel.org
Subject: Re: git-svn and huge data and modifying the git-svn-HEAD branch directly
Date: Wed, 1 Mar 2006 10:25:21 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0603011023080.22647@g5.osdl.org> (raw)
In-Reply-To: <200603011906.33433.Josef.Weidendorfer@gmx.de>
On Wed, 1 Mar 2006, Josef Weidendorfer wrote:
>
> On Wednesday 01 March 2006 18:40, Linus Torvalds wrote:
> > But if somebody does the get_sha1() magic, and Junio agrees, then I think
> > it would be a great thing to do.
>
> Yes.
>
> git log origin/master..
>
> is really not that bad
It really is.
Think like a user. If I pull from "origin", then the name of that thing is
"origin", not "origin/master" or "o/master". A user doesn't care what the
remote branch name is - the whole _point_ of the .git/remotes/xyzzy file
is to give a short description that includes the names of the branches you
pull from.
The good news is that "get_sha1()" shouldn't be that hard to extend on.
Just add a case at the end that says "do we have a .git/remotes/%s file,
and if so, parse it".
Linus
next prev parent reply other threads:[~2006-03-01 18:25 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 17:59 git-svn and huge data and modifying the git-svn-HEAD branch directly Nicolas Vilz 'niv'
2006-02-27 18:46 ` Eric Wong
2006-02-27 18:55 ` Jan Harkes
2006-02-27 19:24 ` Eric Wong
2006-02-28 0:25 ` Martin Langhoff
2006-02-28 0:41 ` Linus Torvalds
2006-02-28 0:58 ` Martin Langhoff
2006-03-01 6:51 ` Eric Wong
2006-03-01 9:40 ` Andreas Ericsson
2006-03-01 15:53 ` Linus Torvalds
2006-03-01 16:07 ` Andreas Ericsson
2006-03-01 16:24 ` Linus Torvalds
2006-03-01 17:14 ` Josef Weidendorfer
2006-03-01 17:28 ` Shawn Pearce
2006-03-01 17:40 ` Linus Torvalds
2006-03-01 18:06 ` Josef Weidendorfer
2006-03-01 18:25 ` Linus Torvalds [this message]
2006-03-01 20:26 ` Josef Weidendorfer
2006-03-01 21:28 ` Linus Torvalds
2006-03-01 19:11 ` Junio C Hamano
2006-03-01 20:54 ` Josef Weidendorfer
2006-03-01 21:40 ` Martin Langhoff
2006-03-01 23:23 ` Carl Worth
2006-03-01 23:43 ` Linus Torvalds
2006-03-01 21:07 ` Johannes Schindelin
2006-03-19 19:12 ` Petr Baudis
2006-03-19 19:35 ` Linus Torvalds
2006-03-19 19:43 ` Junio C Hamano
2006-02-27 19:04 ` [PATCH] contrib/git-svn: tell the user to not modify git-svn-HEAD directly Eric Wong
2006-02-27 19:34 ` git-svn and huge data and modifying the git-svn-HEAD branch directly Nicolas Vilz 'niv'
2006-02-27 20:27 ` Eric Wong
2006-02-27 20:47 ` Nicolas Vilz 'niv'
2006-02-27 20:55 ` [PATCH] contrib/git-svn: correct commit example in manpage Eric Wong
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=Pine.LNX.4.64.0603011023080.22647@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=Josef.Weidendorfer@gmx.de \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
--cc=normalperson@yhbt.net \
/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).