Stefan Richter <[EMAIL PROTECTED]> writes:
> Jan Engelhardt wrote:
>>> http://linux.yyz.us/git-howto.html
>>
>> It says
>>
>> """Don't forget to download tags from time to time.
>>
>> git pull only downloads sha1-indexed object data, and the requested
>> remote head. This misses updates to
Jan Engelhardt wrote:
>> http://linux.yyz.us/git-howto.html
>
> It says
>
> """Don't forget to download tags from time to time.
>
> git pull only downloads sha1-indexed object data, and the requested
> remote head. This misses updates to the .git/refs/tags/ and
> .git/refs/heads/ directorie
On Dec 23 2007 06:13, Jeff Garzik wrote:
> Another year, another update! :)
>
> The kernel hacker's guide to git has received some updates:
>
> http://linux.yyz.us/git-howto.html
>
It says
"""Don't forget to download tags from time to time.
git pull only downloads sha1-indexed object dat
On Sun, 23 Dec 2007, Dieter Ries wrote:
> Could you perhaps publish your reference list as kind of a christmas
> gift to all basic users like me?
FYI, i'm typing in my own reference list as we speak here:
http://www.crashcourse.ca/wiki/index.php/Git
still quite a bit to go, but you can get th
On Sun, Dec 23, 2007 at 06:13:03AM -0500, Jeff Garzik <[EMAIL PROTECTED]> wrote:
> Another year, another update! :)
>
> The kernel hacker's guide to git has received some updates:
>
> http://linux.yyz.us/git-howto.html
one minor note:
i would suggest using:
$ git shortlog master..HEAD
Dieter Ries wrote:
> Robert P. J. Day schrieb:
>> when i got started with git, what i really wanted
>> was a list of what i (as a simple, non-developer user) could do once i
>> cloned a repository.
>>
>> to that end, i put together my own little reference list of git
>> commands. for example, i co
On Sun, 23 Dec 2007, Dieter Ries wrote:
> Robert P. J. Day schrieb:
> > just to be clear, i'm not complaining about the quality of the
> > document above, but when i got started with git, what i really
> > wanted was a list of what i (as a simple, non-developer user)
> > could do once i cloned a
Robert P. J. Day schrieb:
> On Sun, 23 Dec 2007, Jeff Garzik wrote:
>
>> Robert P. J. Day wrote:
>>> On Sun, 23 Dec 2007, Jeff Garzik wrote:
>>>
Another year, another update! :)
The kernel hacker's guide to git has received some updates:
http://linux.yyz.us/git-howto.h
On Sun, Dec 23, 2007 at 06:13:03AM -0500, Jeff Garzik wrote:
>Another year, another update! :)
>
>The kernel hacker's guide to git has received some updates:
>
> http://linux.yyz.us/git-howto.html
>
>This includes all the input sent to me in the past several months, as
>well as a few new ti
On Sun, 23 Dec 2007, Jeff Garzik wrote:
> Robert P. J. Day wrote:
> > On Sun, 23 Dec 2007, Jeff Garzik wrote:
> >
> > > Another year, another update! :)
> > >
> > > The kernel hacker's guide to git has received some updates:
> > >
> > > http://linux.yyz.us/git-howto.html
> > >
> > > This includ
Robert P. J. Day wrote:
On Sun, 23 Dec 2007, Jeff Garzik wrote:
Another year, another update! :)
The kernel hacker's guide to git has received some updates:
http://linux.yyz.us/git-howto.html
This includes all the input sent to me in the past several months,
as well as a few new tip
On Sun, 23 Dec 2007, Jeff Garzik wrote:
> Another year, another update! :)
>
> The kernel hacker's guide to git has received some updates:
>
> http://linux.yyz.us/git-howto.html
>
> This includes all the input sent to me in the past several months,
> as well as a few new tips and tricks I u
Jeff Garzik <[EMAIL PROTECTED]> wrote:
> I refreshed my git intro/cookbook for kernel hackers, at
> http://linux.yyz.us/git-howto.html
Looks nice, starting to look it over.
Notes:
Getting started:
There are RPM packages available (I think they are for latest Fedora; in
case of doubt get the
On 21/12/06, Jeff Garzik <[EMAIL PROTECTED]> wrote:
I refreshed my git intro/cookbook for kernel hackers, at
http://linux.yyz.us/git-howto.html
This describes most of the commands I use in day-to-day kernel hacking.
Let me know if there are glaring errors or missing key commands.
Very nice.
Hi.
On Thu, 2006-12-21 at 06:44 -0500, Jeff Garzik wrote:
> Nigel Cunningham wrote:
> > Hi.
> >
> > On Wed, 2006-12-20 at 22:04 -0500, Jeff Garzik wrote:
> >> I refreshed my git intro/cookbook for kernel hackers, at
> >> http://linux.yyz.us/git-howto.html
> >>
> >> This describes most of the com
Guennadi Liakhovetski wrote:
On Wed, 20 Dec 2006, Jeff Garzik wrote:
I refreshed my git intro/cookbook for kernel hackers, at
http://linux.yyz.us/git-howto.html
Very nice, thanks! A couple of remarks from an absolute git newbie:
1. I heard "git am" is supposed to supersede apply-mbox
Hey,
On Wed, 20 Dec 2006, Jeff Garzik wrote:
> I refreshed my git intro/cookbook for kernel hackers, at
> http://linux.yyz.us/git-howto.html
Very nice, thanks! A couple of remarks from an absolute git newbie:
1. I heard "git am" is supposed to supersede apply-mbox
2. What I often have problems with
Jeff Garzik <[EMAIL PROTECTED]> :
> I refreshed my git intro/cookbook for kernel hackers, at
> http://linux.yyz.us/git-howto.html
>
> This describes most of the commands I use in day-to-day kernel hacking.
> Let me know if there are glaring errors or missing key commands.
o 'git whatchanged sh
Nigel Cunningham wrote:
Hi.
On Wed, 2006-12-20 at 22:04 -0500, Jeff Garzik wrote:
I refreshed my git intro/cookbook for kernel hackers, at
http://linux.yyz.us/git-howto.html
This describes most of the commands I use in day-to-day kernel hacking.
Let me know if there are glaring errors or m
Hi.
On Wed, 2006-12-20 at 22:04 -0500, Jeff Garzik wrote:
> I refreshed my git intro/cookbook for kernel hackers, at
> http://linux.yyz.us/git-howto.html
>
> This describes most of the commands I use in day-to-day kernel hacking.
> Let me know if there are glaring errors or missing key comman
Hi Jeff !
On Wed, Dec 20, 2006 at 10:04:17PM -0500, Jeff Garzik wrote:
> I refreshed my git intro/cookbook for kernel hackers, at
> http://linux.yyz.us/git-howto.html
Thanks for this update, it was my most useful source of inspiration
when I started with git.
> This describes most of the comman
21 matches
Mail list logo