git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Git Mailing List <git@vger.kernel.org>, Peter Anvin <hpa@zytor.com>
Subject: Re: Re-done kernel archive - real one?
Date: Sun, 17 Apr 2005 09:36:09 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0504170926410.7211@ppc970.osdl.org> (raw)
In-Reply-To: <20050417162448.A13233@flint.arm.linux.org.uk>



On Sun, 17 Apr 2005, Russell King wrote:
>
> On Sat, Apr 16, 2005 at 04:01:45PM -0700, Linus Torvalds wrote:
> > So I re-created the dang thing (hey, it takes just a few minutes), and
> > pushed it out, and there's now an archive on kernel.org in my public
> > "personal" directory called "linux-2.6.git". I'll continue the tradition
> > of naming git-archive directories as "*.git", since that really ends up
> > being the ".git" directory for the checked-out thing.
> 
> We need to work out how we're going to manage to get our git changes to
> you.  At the moment, I've very little idea how to do that.  Ideas?

To me, merging is my highest priority. I suspect that once I have a tree 
from you (or anybody else) that I actually _test_ merging with, I'll be 
motivated as hell to make sure that my plumbing actually works. 

After all, it's not just you who want to have to avoid the pain of 
merging: it's definitely in my own best interests to make merging as 
easy as possible. You're _the_ most obvious initial candidate, because 
your merges almost never have any conflicts at all, even on a file level 
(much less within a file).

> However, I've made a start to generate the necessary emails.  How about
> this format?
> 
> I'm not keen on the tree, parent, author and committer objects appearing
> in this - they appear to clutter it up.  What're your thoughts?

Indeed. I'd almost drop the whole header except for the "author" line. 

Oh, and you need a separator between commits, right now your 
"Signed-off-by:" line ends up butting up with the header of the next 
commit ;)

> I'd rather not have the FQDN of the machine where the commit happened
> appearing in the logs.

That's fine. Out short-logs have always tried to have just the real name 
in them, and I do want an email-like thing for tracking the developer, but 
yes, if you remove the email, that's fine. It should be easy enough to do 
with a simple

	sed 's/<.*>//'

or similar.

And if you replace "author" with "From:" and do the date conversion, it
might look more natural.

		Linus

  parent reply	other threads:[~2005-04-17 16:30 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-16 23:01 Re-done kernel archive - real one? Linus Torvalds
2005-04-17 15:24 ` Russell King
2005-04-17 16:28   ` Petr Baudis
2005-04-17 16:36   ` Linus Torvalds [this message]
2005-04-17 18:57     ` Russell King
2005-04-17 19:33       ` Linus Torvalds
2005-04-17 19:45         ` Linus Torvalds
2005-04-17 19:51         ` Russell King
2005-04-17 20:08           ` Linus Torvalds
2005-04-17 20:11             ` Russell King
2005-04-17 20:26               ` Linus Torvalds
2005-04-17 20:42                 ` Russell King
2005-04-18 22:16       ` Russell King
2005-04-18 22:33         ` Petr Baudis
2005-04-18 23:29         ` Linus Torvalds
2005-04-18 23:53         ` Petr Baudis
2005-04-17 16:05 ` Russell King
2005-04-17 16:44   ` Linus Torvalds
2005-04-17 18:13     ` David A. Wheeler
2005-04-17 18:14       ` Petr Baudis
2005-04-17 18:20       ` Russell King
2005-04-17 18:44         ` David A. Wheeler
2005-04-18 11:15         ` Martin Schlemmer
2005-04-17 20:21 ` H. Peter Anvin
2005-04-17 21:50 ` Jochen Roemling
2005-04-17 22:09   ` Randy.Dunlap
2005-04-17 22:30     ` Petr Baudis
2005-04-17 21:52 ` David Woodhouse
2005-04-17 22:17   ` Linus Torvalds
2005-04-17 22:19     ` Russell King
2005-04-17 22:51       ` Russell King
2005-04-17 23:24         ` Linus Torvalds
2005-04-18  9:23           ` Russell King
2005-04-18 11:14             ` Martin Schlemmer
2005-04-18 11:15             ` Petr Baudis
2005-04-18 15:23             ` Linus Torvalds
2005-04-18 17:05               ` Linus Torvalds
2005-04-18 18:07                 ` Petr Baudis
2005-04-18 21:53               ` Russell King
2005-04-18 22:01                 ` Linus Torvalds
2005-04-18 22:48                 ` Petr Baudis
2005-04-18 22:59                   ` Russell King
2005-04-18 23:09                     ` Petr Baudis
2005-04-19  7:27                       ` Russell King
2005-04-18 23:31                   ` Linus Torvalds
2005-04-18 21:33             ` Russell King
2005-04-18 21:56               ` Linus Torvalds
2005-04-18 14:22           ` Petr Baudis
2005-04-18 15:04           ` Greg KH
2005-04-18 15:25             ` Randy.Dunlap
2005-04-18 15:42             ` Linus Torvalds
2005-04-18 22:05               ` Greg KH
2005-04-18 22:14                 ` Greg KH
2005-04-18 23:16                   ` Linus Torvalds
2005-04-18 23:26                     ` Greg KH
2005-04-18 23:10                 ` Linus Torvalds
2005-04-17 22:20     ` H. Peter Anvin
2005-04-17 22:22     ` randy_dunlap
2005-04-17 23:21       ` David Woodhouse
2005-04-18  1:33         ` randy_dunlap

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.58.0504170926410.7211@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=git@vger.kernel.org \
    --cc=hpa@zytor.com \
    --cc=rmk@arm.linux.org.uk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).