Re: Everday contents

2014-08-04 Thread Junio C Hamano
Philip Oakley philipoak...@iee.org writes:

 From: Junio C Hamano gits...@pobox.com
 Philip Oakley philipoak...@iee.org writes:

 From: Junio C Hamano gits...@pobox.com
 Sent: Friday, July 25, 2014 11:08 PM
 ...

 | Individual Developer (Participant)[[Individual Developer
 (Participant)]]
 | 

 ...
 | $ git pull git://git.kernel.org/pub/.../jgarzik/libata-dev.git ALL
 5

 Would I be right that ALL can simply be dropped as something from
 back then' (13 Dec 2005 v0.99.9-516-g44db136) that I'm ignorant of?

 The answer depends on the reason why you want to drop it from the
 example.

 That ALL is merely a branch name, like master, etc.

 That was the bit I was missing. I had it in my head that it was
 possibly some historic option as it was in caps.

Yeah, I suspected as much ;-)  Thanks for a careful reading.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Everday contents

2014-08-03 Thread Junio C Hamano
Philip Oakley philipoak...@iee.org writes:

 From: Junio C Hamano gits...@pobox.com
 Sent: Friday, July 25, 2014 11:08 PM
 ...

 | Individual Developer (Participant)[[Individual Developer
 (Participant)]]
 | 

 ...
 | $ git pull git://git.kernel.org/pub/.../jgarzik/libata-dev.git ALL
 5

 Would I be right that ALL can simply be dropped as something from
 back then' (13 Dec 2005 v0.99.9-516-g44db136) that I'm ignorant of?

The answer depends on the reason why you want to drop it from the
example.

That ALL is merely a branch name, like master, etc.  I do not
know how jgarzik names his published branches these days, but back
then ALL there was something that contained all the topics he wanted
others to look at.  And the description of 5 explains it to be
fetching a specific branch, so that needs to be reworded if we are
to change the example to from the default branch of a specific
repository or something.

 ...
 | 5 fetch from a specific branch from a specific repository and
 merge.

Thanks.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Everday contents

2014-08-03 Thread Philip Oakley

From: Junio C Hamano gits...@pobox.com

Philip Oakley philipoak...@iee.org writes:


From: Junio C Hamano gits...@pobox.com
Sent: Friday, July 25, 2014 11:08 PM
...


| Individual Developer (Participant)[[Individual Developer
(Participant)]]
| 


...

| $ git pull git://git.kernel.org/pub/.../jgarzik/libata-dev.git ALL
5


Would I be right that ALL can simply be dropped as something from
back then' (13 Dec 2005 v0.99.9-516-g44db136) that I'm ignorant of?


The answer depends on the reason why you want to drop it from the
example.

That ALL is merely a branch name, like master, etc.


That was the bit I was missing. I had it in my head that it was possibly 
some historic option as it was in caps.



 I do not
know how jgarzik names his published branches these days, but back
then ALL there was something that contained all the topics he wanted
others to look at.  And the description of 5 explains it to be
fetching a specific branch, so that needs to be reworded if we are


I eventually went with using a lower case 'dev' as a nominal branch 
name, and also named it in the updated 5. However I hadn't actually 
checked if the repos is still active.



to change the example to from the default branch of a specific
repository or something.


...

| 5 fetch from a specific branch from a specific repository and
merge.




Thanks.

Philip 


--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Everday contents (was part of Re: What's cooking in git.git (Jul 2014, #04; Tue, 22))

2014-08-02 Thread Philip Oakley

From: Junio C Hamano gits...@pobox.com
Sent: Friday, July 25, 2014 11:08 PM
...


| Individual Developer (Participant)[[Individual Developer 
(Participant)]]

| 


...
| $ git pull git://git.kernel.org/pub/.../jgarzik/libata-dev.git ALL 
5


Would I be right that ALL can simply be dropped as something from 
'back then' (13 Dec 2005 v0.99.9-516-g44db136) that I'm ignorant of?


...
| 5 fetch from a specific branch from a specific repository and 
merge.

| 6 revert the pull.
| 7 garbage collect leftover objects from reverted pull.
| 8 from time to time, obtain official tags from the `origin`
| and store them under `.git/refs/tags/`.

This example works directly on 'master', which is not ideal.  If I
were writing this today, I would have made it work on 'mine' branch,
produced a patch series out of that branch relative to @{u}, threw
in 'git send-email' invocation, and had git pull update the
pristine 'mater' branch after git checkout master.  Merging of
work by jgarzik (i.e. not your upstream) would also have gone to its
own branch, not to 'master'.


Slowly working through it ;-)

Ta.

Philip 


--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html