From: Petr Baudis <pasky@ucw.cz>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH 0/4] Pulling refs files
Date: Sat, 14 May 2005 00:19:35 +0200 [thread overview]
Message-ID: <20050513221935.GC32232@pasky.ji.cz> (raw)
In-Reply-To: <Pine.LNX.4.21.0505130245260.30848-100000@iabervon.org>
Dear diary, on Fri, May 13, 2005 at 08:49:25AM CEST, I got a letter
where Daniel Barkalow <barkalow@iabervon.org> told me that...
> This series makes the following changes:
>
> 1: Adds support for having the C code know about the general existance of
> .git/refs, and functions for writing these files.
> 2: Adds support in the generic pull code for fetching refs (and dummy
> implementations).
> 3: Adds support in the HTTP pull code for fetching refs
> 4: Adds support in the rsh pull code for fetching refs; this requires
> changes to the protocol. These changes should be sufficient to support
> any future extension, however.
Hmm, I've honestly expected something different - a generic way to
specify any file in the repository to be pulled along, instead of a
introducing refs awareness at this level of git. What would be the
advantages of that approach against just specifying list of other files
to pull along?
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
next prev parent reply other threads:[~2005-05-13 22:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 6:49 [PATCH 0/4] Pulling refs files Daniel Barkalow
2005-05-13 6:53 ` [PATCH 1/4] Support for refs directory Daniel Barkalow
2005-05-13 6:56 ` [PATCH 2/4] Generic support for pulling refs Daniel Barkalow
2005-05-13 6:57 ` [PATCH 3/4] Pull refs by HTTP Daniel Barkalow
2005-05-13 11:15 ` Edgar Toernig
2005-05-13 7:01 ` [PATCH 4/4] Pulling refs by ssh Daniel Barkalow
2005-05-13 18:59 ` H. Peter Anvin
2005-05-15 15:48 ` Daniel Barkalow
2005-05-13 22:19 ` Petr Baudis [this message]
2005-05-13 23:14 ` [PATCH 0/4] Pulling refs files Daniel Barkalow
2005-05-13 23:37 ` Petr Baudis
2005-05-15 3:23 ` Daniel Barkalow
2005-05-17 20:14 ` Petr Baudis
2005-05-17 21:20 ` Daniel Barkalow
2005-05-17 21:45 ` Petr Baudis
2005-05-17 22:20 ` Daniel Barkalow
2005-05-18 21:35 ` Petr Baudis
2005-05-19 3:19 ` Daniel Barkalow
2005-05-19 6:52 ` Petr Baudis
2005-05-19 16:00 ` Daniel Barkalow
2005-05-15 5:33 ` Junio C Hamano
2005-05-15 15:40 ` Daniel Barkalow
2005-05-16 7:55 ` 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
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=20050513221935.GC32232@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--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.
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).