From: Pat Notz <patnotz@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>, Git <git@vger.kernel.org>
Subject: Re: Gnome chose Git
Date: Thu, 19 Mar 2009 08:01:32 -0600 [thread overview]
Message-ID: <1cd1989b0903190701uac4602dl1d2c3cace45a9938@mail.gmail.com> (raw)
In-Reply-To: <49C24D9B.1060301@drmicha.warpmail.net>
On Thu, Mar 19, 2009 at 7:50 AM, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
> Pat Notz venit, vidit, dixit 19.03.2009 14:43:
>> On Thu, Mar 19, 2009 at 7:33 AM, Michael J Gruber
>> <git@drmicha.warpmail.net> wrote:
>>> Teemu Likonen venit, vidit, dixit 19.03.2009 12:23:
>>>> FYI: The Gnome release team just announced that Gnome will migrate from
>>>> Subversion to Git:
>>>>
>>>> http://thread.gmane.org/gmane.comp.gnome.infrastructure/1134
>>>
>>> Good choice :)
>>>
>>> Interestingly, they seem to go the svn-all-fast-export route.
>>>
>>> Also, they need push tracking for pushing through ssh, which is a common
>>> requirement for many large projects. Do we have something to support
>>> that? git-notes comes to my mind.
>>>
>>> Their current approach is writing to a single log file (receive-hook).
>>> That may support a linear push history best, but looking up who pushed
>>> what, given "what"?
>>>
>>
>> That's also something we do. Since the post-receive hook gives you
>> the refname and the old and new refs you should have everything you
>> need. We basically record the user name, UTC timestamp and the ref
>> info. With a little bit more scripting you should be able to figure
>> everything else out (though post-receive isn't called for local
>> commits).
>>
>
> I know the info is there. It might just make more sense to have it in
> the git repo the way notes are/will be: It's public, it's connected to
> the commits, it's tamper proof (anyone would notice rewrites).
>
Ahh, yes. We'd like that too.
> Michael
>
> P.S.: Was this intentionally off-list? Just in case I respected it.
>
Oops, sorry about that. Fixed.
next prev parent reply other threads:[~2009-03-19 14:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 11:23 Gnome chose Git Teemu Likonen
2009-03-19 11:29 ` Sverre Rabbelier
2009-03-19 11:33 ` Mike Ralphson
2009-03-19 16:29 ` Andreas Ericsson
2009-03-19 13:33 ` Michael J Gruber
[not found] ` <1cd1989b0903190643p19a40718yc4fd2730aab0a9a0@mail.gmail.com>
[not found] ` <49C24D9B.1060301@drmicha.warpmail.net>
2009-03-19 14:01 ` Pat Notz [this message]
2009-03-19 15:16 ` Shawn O. Pearce
2009-03-19 15:50 ` Pat Notz
2009-03-19 20:14 ` Jeff King
2009-03-19 21:40 ` demerphq
2009-03-19 21:43 ` Shawn O. Pearce
2009-03-19 21:44 ` Shawn O. Pearce
2009-03-19 21:51 ` demerphq
2009-03-19 21:53 ` Shawn O. Pearce
2009-03-19 21:59 ` demerphq
2009-03-19 23:17 ` Johannes Schindelin
2009-03-19 21:48 ` demerphq
2009-03-20 5:28 ` Jeff King
2009-03-20 6:00 ` [PATCH] make oneline reflog dates more consistent with multiline format Jeff King
2009-03-20 8:33 ` Gnome chose Git Michael J Gruber
2009-03-20 20:03 ` Jeff King
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=1cd1989b0903190701uac4602dl1d2c3cace45a9938@mail.gmail.com \
--to=patnotz@gmail.com \
--cc=git@drmicha.warpmail.net \
--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).