git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Barkalow <barkalow@iabervon.org>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>
Subject: [PATCH 0/3] Add "remote" library
Date: Wed, 9 May 2007 22:03:59 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705092149060.18541@iabervon.org> (raw)

This series makes a library for handling remotes, by moving code from less 
appropriate places into a new header and source file pair. It shouldn't 
have any major changes in behavior at this point, aside from a few 
behavior improvements ("git push not-a-remote-name" before would give the 
wrong error message; newer configuration methods should override older 
ones; we should use the same default remote for push that we do for pull, 
all else being equal).

Patches 1 and 2 mostly move code into remote.c from other files. Patch 3 
adds useful code for the fetch side, corresponding to the code for the 
push side, but this code isn't used yet, because the code that would use 
it is still in shell. Patches 1 and 2 make sense without patch 3, however.

	-Daniel
*This .sig left intentionally blank*

                 reply	other threads:[~2007-05-10  2:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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.0705092149060.18541@iabervon.org \
    --to=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.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).