Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
	git@vger.kernel.org, Petr Baudis <pasky@ucw.cz>
Subject: Re: Complete http-pull; where should it go?
Date: Sun, 01 May 2005 17:09:49 -0700	[thread overview]
Message-ID: <7vsm16qyia.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0505011638370.22864@ppc970.osdl.org> (Linus Torvalds's message of "Sun, 1 May 2005 16:48:04 -0700 (PDT)")

>>>>> "LT" == Linus Torvalds <torvalds@osdl.org> writes:

LT> I didn't do the ".p1" for parent thing. It would be easy to add, I just 
LT> haven't decided on a nice syntax for it (I'd like something that is nice 
LT> and doesn't need quoting, but the ".p1" seems a bit _too_ ugly).

Shameless plug but could you take a look at how my JIT does it,
at <http://members.cox.net/junkio/JITNotes.txt>, especially
scroll down to near the bottom "Syntax to naming a snapshot or a
commit" section?

I still think this kind of thing belongs to Porcelain not
Plumbing, though.


  reply	other threads:[~2005-05-02  0:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-01 19:29 Complete http-pull; where should it go? Daniel Barkalow
2005-05-01 19:44 ` Linus Torvalds
2005-05-01 20:30   ` Daniel Barkalow
2005-05-01 20:46     ` Linus Torvalds
2005-05-01 21:25       ` Daniel Barkalow
2005-05-01 23:23         ` Linus Torvalds
2005-05-01 23:46           ` Daniel Barkalow
2005-05-01 23:48           ` Linus Torvalds
2005-05-02  0:09             ` Junio C Hamano [this message]
2005-05-02  1:50               ` Linus Torvalds
2005-05-02  2:03                 ` Junio C Hamano
2005-05-02  2:43                   ` Linus Torvalds
2005-05-02  2:31                 ` Daniel Barkalow
2005-05-01 21:25       ` Junio C Hamano

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=7vsm16qyia.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=pasky@ucw.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox