git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sverre Hvammen Johansen" <hvammen@gmail.com>
To: git@vger.kernel.org
Subject: Re: [RFC/PATCH] Fast forward strategies only, common, fork and path
Date: Sun, 3 Feb 2008 23:13:50 -0800	[thread overview]
Message-ID: <402c10cd0802032313la7d3a8cqa4ec34e100385fb4@mail.gmail.com> (raw)
In-Reply-To: <402c10cd0802031654r3e0275a8s1d2163af9525e7d2@mail.gmail.com>

git-pull only accepts one repository.  With this patch it makes sense
to accept more than one repository.  I would like to rewrite git-pull
to accept more than one repository.  This might break compatibility
with existing git-pull.  One solution could be to introduce a new
command that does the same as git-pull and more.  What about naming
such a command git-update and deprecate git-pull.

I believe such an command should not specify the repository and the
refspec but should instead specify the remote tracking branch or a
local branch if descired.  I believe this would be more natural to use
and just as easier to implement.

-- 
Sverre Hvammen Johansen

  parent reply	other threads:[~2008-02-04  7:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04  0:54 [RFC/PATCH] Fast forward strategies only, common, fork and path Sverre Hvammen Johansen
2008-02-04  4:49 ` Stefan (metze) Metzmacher
2008-02-04  6:51 ` Sverre Hvammen Johansen
2008-02-04  7:24   ` Junio C Hamano
2008-02-04  8:06     ` Sverre Hvammen Johansen
2008-02-04  8:22       ` Junio C Hamano
2008-02-05  7:32         ` Sverre Hvammen Johansen
2008-02-05  9:34           ` Jakub Narebski
2008-02-05  9:40           ` Junio C Hamano
2008-02-06  3:46             ` Sverre Hvammen Johansen
2008-02-04  7:13 ` Sverre Hvammen Johansen [this message]
2008-02-04  7:31   ` Junio C Hamano
2008-02-04  7:43     ` Sverre Hvammen Johansen
2008-02-04  7:19 ` Sverre Hvammen Johansen

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=402c10cd0802032313la7d3a8cqa4ec34e100385fb4@mail.gmail.com \
    --to=hvammen@gmail.com \
    --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).