--
On Sun, Oct 5, 2014 02:02 BST Eric Wong wrote:
>Eric Wong wrote:
>> Jakob sent some patches a few months ago which seem to address the
>> issue. Unfortunately we forgot about them :x
>
>Hin-Tak: have you tried Jakob's patches? I've taken another look,
>signed-off
On 10/7/2014 12:58 AM, Junio C Hamano wrote:
>
> The point is to prevent"git config --add foo.baz anothervalue" starting from
>
> --- --- ---
> [foo]
> bar = some
> [unset] variable = foo.baz
> --- --- ---
>
> from adding foo.baz next to existing foo.bar. We would want to end up with
>
> ---
On Mon, Oct 6, 2014 at 11:59 AM, Tanay Abhra wrote:
> 3> Special case "unset.variable", so that git config unset.variable foo.baz
> pastes it on the top of the file. The implementation should be trivial, but,
> Junio had said in an earlier mail that he doesn't think this approach would
> do much g
On 10/4/2014 1:42 AM, Junio C Hamano wrote:
> Matthieu Moy writes:
>
>> Junio C Hamano writes:
Well, the normal use-case for unset.variable is to put it in a local
config file, to unset a variable set in another, lower-priority file.
>>>
>>> I agree that is one major use case.
>>>
Am 06.10.2014 um 07:17 schrieb Marat Radchenko:
> On Tue, Sep 30, 2014 at 11:02:29AM +0400, Marat Radchenko wrote:
>> This patch series fixes building on modern MinGW and MinGW-W64 (including
>> x86_64!).
>
> Junio, ping?
>
Sorry, I forgot to report that this updated series works now for me.
T
On Mon, 6 Oct 2014, Patrick Donnelly wrote:
There are efforts in the scientific communities at preserving
experimental software and results. One of the things we'd like to do
is shallow clone a specific sha1 commit from e.g. GitHub. [I think
GitHub has this disabled though? I haven't been able t
On Thu, Oct 2, 2014 at 12:10 PM, Jeff King wrote:
> On Thu, Oct 02, 2014 at 10:22:50AM -0400, Dan Johnson wrote:
>> My understanding is that you are allowed to ask for a SHA1, but most
>> git servers refuse the request. But if you already have the SHA
>> locally, then git doesn't neet to bother as
Rasmus Villemoes writes:
> Junio C Hamano wrote:
>
>> (by the way, we do not do dashes in names for configuration by
>> convention)
>
> OK. Actually, I now think I'd prefer a subsection [include "safe"], but
> I don't have any strong preferences regarding the names.
I think Peff mentioned somet
Kedves Email felhasználói
Túllépte 23.432 doboz állította be
Web Services / menedzser, és akkor lesz probléma küldő és
e-mailt kap, míg újra ellenőrizni. Frissítenie kell
Kattintson
hivatkozásra, és az alábbi információkat, hogy ellenőrizze a számla
Kérjük, kattintson az alábbi linkre, vagy másolj
Junio C Hamano wrote:
> (by the way, we do not do dashes in names for configuration by
> convention)
OK. Actually, I now think I'd prefer a subsection [include "safe"], but
I don't have any strong preferences regarding the names.
> That syntax _could_ be just a relative path (e.g. project.gitco
10 matches
Mail list logo
