From: Peter Eriksen <s022018@student.dtu.dk>
To: linux-kernel@vger.kernel.org
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.4.3
Date: 20 Oct 2006 15:26:04 +0200 [thread overview]
Message-ID: <m3zmbrt8yb.fsf@localhost.localdomain> (raw)
In-Reply-To: 7vejt5xjt9.fsf@assigned-by-dhcp.cox.net
Junio C Hamano <junkio@cox.net> writes:
> The latest feature release GIT 1.4.3 is available at the usual
> places:
...
> ----------------------------------------------------------------
>
> .gitignore | 10 +-
> Documentation/Makefile | 4 +-
> Documentation/asciidoc.conf | 1 +
> Documentation/config.txt | 34 +
...
> rename contrib/gitview/{gitview.txt => gitview.txt} (74%)
How does it come to the result, that this is a rename?
Peter
WARNING: multiple messages have this Message-ID (diff)
From: Peter Eriksen <s022018@student.dtu.dk>
To: git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.4.3
Date: 20 Oct 2006 15:26:04 +0200 [thread overview]
Message-ID: <m3zmbrt8yb.fsf@localhost.localdomain> (raw)
In-Reply-To: 7vejt5xjt9.fsf@assigned-by-dhcp.cox.net
Junio C Hamano <junkio@cox.net> writes:
> The latest feature release GIT 1.4.3 is available at the usual
> places:
...
> ----------------------------------------------------------------
>
> .gitignore | 10 +-
> Documentation/Makefile | 4 +-
> Documentation/asciidoc.conf | 1 +
> Documentation/config.txt | 34 +
...
> rename contrib/gitview/{gitview.txt => gitview.txt} (74%)
How does it come to the result, that this is a rename?
Peter
next prev parent reply other threads:[~2006-10-20 13:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 23:53 [ANNOUNCE] GIT 1.4.3 Junio C Hamano
2006-10-20 12:31 ` Horst H. von Brand
2006-10-20 13:26 ` Peter Eriksen [this message]
2006-10-20 13:26 ` Peter Eriksen
2006-10-20 23:35 ` Junio C Hamano
2006-10-21 0:14 ` Linus Torvalds
2006-10-21 0:22 ` Petr Baudis
2006-10-21 0:31 ` Linus Torvalds
2006-10-21 9:53 ` Andreas Schwab
2006-10-22 21:09 ` Anders Larsen
2006-10-22 21:09 ` Anders Larsen
2006-10-21 2:12 ` Al Viro
2006-10-21 5:29 ` Junio C Hamano
2006-10-21 5:40 ` Al Viro
2006-10-21 14:29 ` Rene Scharfe
2006-10-21 0:47 ` Nicolas Pitre
2006-10-23 0:53 ` prune/prune-packed J. Bruce Fields
2006-10-23 1:26 ` prune/prune-packed A Large Angry SCM
2006-10-23 2:36 ` [ANNOUNCE] GIT 1.4.3 J. Bruce Fields
2006-10-23 3:27 ` prune/prune-packed Junio C Hamano
2006-10-23 18:39 ` prune/prune-packed Petr Baudis
2006-10-27 21:19 ` prune/prune-packed Jon Loeliger
2006-10-27 21:55 ` prune/prune-packed Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2006-10-22 3:59 prune/prune-packed J. Bruce Fields
2006-10-22 4:59 ` prune/prune-packed Junio C Hamano
2006-10-22 23:14 ` prune/prune-packed J. Bruce Fields
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=m3zmbrt8yb.fsf@localhost.localdomain \
--to=s022018@student.dtu.dk \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.