Felipe Contreras writes:
> There's no mention of the 'origin' default, or the fact that the
> upstream tracking branch remote is used.
>
> Signed-off-by: Felipe Contreras
> ---
> Documentation/git-fetch.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/git-fetch.txt
There's no mention of the 'origin' default, or the fact that the
upstream tracking branch remote is used.
Signed-off-by: Felipe Contreras
---
Documentation/git-fetch.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/git-fetch.txt b/Documentation/git-fetch.txt
index e08a028
On Thu, Oct 31, 2013 at 12:10 PM, Junio C Hamano wrote:
> Felipe Contreras writes:
>> diff --git a/Documentation/git-fetch.txt b/Documentation/git-fetch.txt
>> index e08a028..7e75dc4 100644
>> --- a/Documentation/git-fetch.txt
>> +++ b/Documentation/git-fetch.txt
>> @@ -37,6 +37,9 @@ or from sev
Felipe Contreras writes:
> There's no mention of the 'origin' default, or the fact that the
> upstream tracking branch remote is used.
>
> Signed-off-by: Felipe Contreras
> ---
> Documentation/git-fetch.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/git-fetch.txt
There's no mention of the 'origin' default, or the fact that the
upstream tracking branch remote is used.
Signed-off-by: Felipe Contreras
---
Documentation/git-fetch.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/git-fetch.txt b/Documentation/git-fetch.txt
index e08a028
There's no mention of the 'origin' default, or the fact that the
upstream tracking branch remote is used.
Signed-off-by: Felipe Contreras
---
Documentation/git-fetch.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/git-fetch.txt b/Documentation/git-fetch.txt
index e08a028
On Tue, Sep 24, 2013 at 1:54 AM, Jeff King wrote:
> On Tue, Sep 24, 2013 at 01:31:48AM -0500, Felipe Contreras wrote:
>
>> > I don't think it is the end of the world if we say "upstream branch". I
>> > was hoping to find a term that could be both friendly and accurate.
>> >
>> > And failing that,
On Tue, Sep 24, 2013 at 01:31:48AM -0500, Felipe Contreras wrote:
> > I don't think it is the end of the world if we say "upstream branch". I
> > was hoping to find a term that could be both friendly and accurate.
> >
> > And failing that, I hoped you might say "I see what you are saying, but
> >
On Tue, Sep 24, 2013 at 1:10 AM, Jeff King wrote:
> On Tue, Sep 24, 2013 at 12:57:36AM -0500, Felipe Contreras wrote:
>
>> No, I'm not. The users that know branch.*.remote exists know why it
>> exists. The part where it is explained, 'git config --help', is
>> perfectly clear: "When on branch , it
On Tue, Sep 24, 2013 at 12:57:36AM -0500, Felipe Contreras wrote:
> No, I'm not. The users that know branch.*.remote exists know why it
> exists. The part where it is explained, 'git config --help', is
> perfectly clear: "When on branch , it tells 'git fetch' and 'git
> push' which remote to fetch
On Tue, Sep 24, 2013 at 12:40 AM, Jeff King wrote:
> On Tue, Sep 24, 2013 at 12:36:38AM -0500, Felipe Contreras wrote:
>
>> > Yeah, it's not a term we use elsewhere, so it's not great. Probably
>> > "default remote" would be better, or even just say "branch.*.remote for
>> > the current branch" or
On Tue, Sep 24, 2013 at 12:36:38AM -0500, Felipe Contreras wrote:
> > Yeah, it's not a term we use elsewhere, so it's not great. Probably
> > "default remote" would be better, or even just say "branch.*.remote for
> > the current branch" or something.
>
> Yeah, general users don't know what you a
On Tue, Sep 24, 2013 at 12:30 AM, Jeff King wrote:
> On Tue, Sep 24, 2013 at 12:23:21AM -0500, Felipe Contreras wrote:
>
>> > Should this be "upstream remote" rather than "upstream branch"? I don't
>> > think we should be looking at branch.*.merge at all for git-fetch.
>>
>> As a general user, how
On Tue, Sep 24, 2013 at 12:23:21AM -0500, Felipe Contreras wrote:
> > Should this be "upstream remote" rather than "upstream branch"? I don't
> > think we should be looking at branch.*.merge at all for git-fetch.
>
> As a general user, how do I configure the "upstream remote"?
Yeah, it's not a t
On Tue, Sep 24, 2013 at 12:03 AM, Jeff King wrote:
> On Sat, Sep 21, 2013 at 09:09:22AM -0500, Felipe Contreras wrote:
>
>> There's no mention of the 'origin' default, or the fact that the
>> upstream tracking branch remote is used.
>
> Sounds like a good thing to mention.
>
>> diff --git a/Docume
On Sat, Sep 21, 2013 at 09:09:22AM -0500, Felipe Contreras wrote:
> There's no mention of the 'origin' default, or the fact that the
> upstream tracking branch remote is used.
Sounds like a good thing to mention.
> diff --git a/Documentation/git-fetch.txt b/Documentation/git-fetch.txt
> index e0
There's no mention of the 'origin' default, or the fact that the
upstream tracking branch remote is used.
Signed-off-by: Felipe Contreras
---
Documentation/git-fetch.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/git-fetch.txt b/Documentation/git-fetch.txt
index e08a028
The following is the list of files in the Documentation directory that
have *NO* useful text in them at all.
git-build-rev-cache.txt
git-checkout-script.txt
git-diff-script.txt
git-format-patch-script.txt
git-get-tar-commit-id.txt
git-reset-script.
18 matches
Mail list logo