From: Jan Hudec <bulb@ucw•cz>
To: Marco Costalba <mcostalba@gmail•com>
Cc: Junio C Hamano <junkio@cox•net>, Alex Riesen <raa.lkml@gmail•com>,
git@vger•kernel.org
Subject: Re: [PATCH] Allow fetching references from any namespace
Date: Sun, 13 May 2007 09:24:09 +0200 [thread overview]
Message-ID: <20070513072409.GD8983@efreet.light.src> (raw)
In-Reply-To: <e5bfff550705122048s6772db3as63f6fb23fe7e1bd7@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
On Sun, May 13, 2007 at 05:48:00 +0200, Marco Costalba wrote:
> On 5/12/07, Junio C Hamano <junkio@cox•net> wrote:
> >
> >Sounds like it is not even a regression but just was not
> >supposed to work from the beginning.
> >
> >Not that I think lifting that restriction is a bad idea,
> >though.
> >
> >-
> >To unsubscribe from this list: send the line "unsubscribe git" in
> >the body of a message to majordomo@vger•kernel.org
> >More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
> Please consider that StGIT put patch names under refs/patches and
> probably we don't want to see them.
If you don't add them to the push configuration, you won't see them.
> I'm very sorry but I cannot test my-self because I'm leaving now. I
> have just seen the patch applied in git tree and this thing come to my
> mind.
It does not make them pushed. It just allows pushing them--which is good
thing sometimes (eg. if you use push to backup the repo).
--
Jan 'Bulb' Hudec <bulb@ucw•cz>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-05-13 7:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 20:35 [PATCH] Allow fetching references from any namespace Alex Riesen
2007-05-11 20:54 ` Junio C Hamano
2007-05-12 7:40 ` Alex Riesen
2007-05-12 7:55 ` Junio C Hamano
2007-05-13 3:48 ` Marco Costalba
2007-05-13 7:24 ` Jan Hudec [this message]
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=20070513072409.GD8983@efreet.light.src \
--to=bulb@ucw$(echo .)cz \
--cc=git@vger$(echo .)kernel.org \
--cc=junkio@cox$(echo .)net \
--cc=mcostalba@gmail$(echo .)com \
--cc=raa.lkml@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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