git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [CFH] Remotes conversion script
Date: Mon, 25 Sep 2006 01:06:19 +0200	[thread overview]
Message-ID: <ef730t$dk9$3@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.63.0609242347090.25371@wbgn013.biozentrum.uni-wuerzburg.de

Johannes Schindelin wrote:

> On Sun, 24 Sep 2006, Jakub Narebski wrote:
> 
>> If I remember correctly currently only some functionality provided by
>> remotes file can be provided by [remote] and [branch] sections of git
>> config.
> 
> ... and what might the lacking functionality be?

What about
        Pull: +refs/heads/pu:refs/heads/pu
functionality, i.e. allowing force-update (non fast-forward) fetches?

> .git/remotes/<name>    config
> 
> URL:                   remote.<name>.url
> Pull:                  remote.<name>.fetch
> Push:                  remote.<name>.push
> 
> You can even have multiple entries in the config, and it behaves as if you 
> had multiple lines in .git/remotes/<name>.

And first pull line is default branch to merge, all the rest is marked
as not-for-merge?

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  parent reply	other threads:[~2006-09-24 23:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-24 21:21 [CFH] Remotes conversion script Petr Baudis
2006-09-24 21:39 ` Jakub Narebski
2006-09-24 21:49   ` Johannes Schindelin
2006-09-24 22:57     ` Jakub Narebski
2006-09-24 23:06     ` Jakub Narebski [this message]
2006-09-24 23:18       ` Santi
2006-09-24 21:46 ` Johannes Schindelin
     [not found] ` <8aa486160609241457u40fffdd8h298e44351749bb29@mail.gmail.com>
2006-09-24 22:16   ` Petr Baudis
2006-09-24 22:34     ` Santi
2006-09-24 22:40       ` Petr Baudis
2006-09-24 23:04         ` Jakub Narebski
2006-09-24 23:11           ` Petr Baudis
2006-09-24 23:40             ` Jakub Narebski
2006-09-24 23:50               ` Petr Baudis

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='ef730t$dk9$3@sea.gmane.org' \
    --to=jnareb@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).