a symref
Junio C Hamano (13):
reencode_string(): introduce and use same_encoding()
test: add failing tests for diff --stat to t4049
diff --stat: status of unmodified pair in diff-q is not zero
diff --stat: use file temporary variable to refer to data-files[i]
diff
ot;git diff --stat" output.
* When "--stat-count" hides a diffstat for binary contents, the total
number of added and removed lines at the bottom was computed
incorrectly.
* When "--stat-count" hides a diffstat for unmerged paths, the total
number of affe
--deref SYM to delete a ref through a symbolic ref
that points to it did not remove it correctly.
Changes since v1.8.1-rc0 are as follows:
Jiang Xin (1):
l10n: Update git.pot (5 new, 1 removed messages)
Junio C Hamano (3
Ramsay Jones writes:
> I fetch git from 'git://git.kernel.org/pub/scm/git/git.git' which has
> commit ee26a6e2 ("Git 1.8.1-rc0", 03-12-2012), but is missing the v1.8.1-rc0
> tag. Is this just an oversight ...
Thanks for letting me know; forgot to push out the tag.
--
To unsubscribe from this
Ramsay Jones ram...@ramsay1.demon.co.uk writes:
I fetch git from 'git://git.kernel.org/pub/scm/git/git.git' which has
commit ee26a6e2 (Git 1.8.1-rc0, 03-12-2012), but is missing the v1.8.1-rc0
tag. Is this just an oversight ...
Thanks for letting me know; forgot to push out the tag.
--
To
A release candidate preview, Git v1.8.1-rc0, is now available for
testing at the usual places.
This cycle has been a bit slow (perhaps because it had a major US
holiday to slow people down) but we seem to have managed to apply
reasonably large number of usability improvement changes, with a
A release candidate preview, Git v1.8.1-rc0, is now available for
testing at the usual places.
This cycle has been a bit slow (perhaps because it had a major US
holiday to slow people down) but we seem to have managed to apply
reasonably large number of usability improvement changes, with a
address encoding with respect to rfc822 specials
format-patch tests: check quoting/encoding in To: and Cc: headers
Jeff King (3):
diff_grep: use textconv buffers for add/deleted files
gitweb: escape html in rss title
checkout: print a message when switching unborn branches
title
checkout: print a message when switching unborn branches
Junio C Hamano (9):
builtin/grep.c: make configuration callback more reusable
grep: move the configuration parsing logic to grep.[ch]
grep: move pattern-type bits support to top-level grep.[ch]
revisions
mat='%ci'" did not give the timestamp correctly for
commits created without human readable name on the "committer" line.
* "git show --quiet" ought to be a synonym for "git show -s", but
wasn't.
* "git submodule frotz" was not diagnosed as &qu
):
git-gui: fix a typo in po/ files
Clemens Buchacher (1):
git-gui: fix git-gui crash due to uninitialized variable
Heiko Voigt (1):
git-gui: open console when using --trace on windows
Junio C Hamano (1):
Git 1.8.0
Marcus Karlsson (1):
git-gui: Use PWD if it exists
was error prone. It
asked "What e-mail address do you want to use?" with the address it
guessed (correctly) the user would want to use in its prompt,
tempting the user to say "y". But the response was taken as "No,
please use 'y' as the e-mail address instead
e: Allow custom XMLTO binary
Dylan Alex Simon (1):
gitweb.cgi: fix "comitter_tz" typo in feed
Jeff King (1):
http: fix segfault in handle_curl_result
Junio C Hamano (6):
merge: teach -Xours/-Xtheirs to binary ll-merge driver
attr: "binary" attribute sh
):
http: fix segfault in handle_curl_result
Junio C Hamano (6):
merge: teach -Xours/-Xtheirs to binary ll-merge driver
attr: binary attribute should choose built-in binary merge driver
ll-merge: warn about inability to merge binary files only when we can't
t1450: the order
messages)
Junio C Hamano (3):
Update draft release notes to 1.8.0
Git 1.7.12.4
Git 1.8.0-rc3
Peter Krefting (1):
l10n: Update Swedish translation (1964t0f0u)
Richard Fearn (1):
Fix spelling error in post-receive-email hook
Thomas Ackermann (1):
Documentation
empty peg rev
Junio C Hamano (2):
gitcli: parse-options lets you omit tail of long options
Git 1.8.0-rc2
Nguyễn Thái Ngọc Duy (2):
gitignore.txt: suggestions how to get literal # or ! at the beginning
attr: a note about the order of .gitattributes lookup
Ramkumar Rama
rev
Junio C Hamano (2):
gitcli: parse-options lets you omit tail of long options
Git 1.8.0-rc2
Nguyễn Thái Ngọc Duy (2):
gitignore.txt: suggestions how to get literal # or ! at the beginning
attr: a note about the order of .gitattributes lookup
Ramkumar Ramachandra (1
tempting the user to say "y". But the response was taken as "No,
please use 'y' as the e-mail address instead", which is most
certainly not what the user meant.
* "git show --format='%ci'" did not give the timestamp correctly for
commits created without human rea
receive-pack: redirect unpack-objects stdout to /dev/null
receive-pack: send pack-processing stderr over sideband
receive-pack: drop "n/a" on unpacker errors
Junio C Hamano (3):
git blame: document that it always follows origin across whole-file
renames
Start preparing fo
.
Changes since v1.7.12.2 are as follows:
Jeff King (3):
receive-pack: redirect unpack-objects stdout to /dev/null
receive-pack: send pack-processing stderr over sideband
receive-pack: drop n/a on unpacker errors
Junio C Hamano (3
Jonathan Nieder (2):
Git::SVN: rename private path field
git-svn: keep leading slash when canonicalizing paths (fallback case)
Junio C Hamano (7):
log --grep-reflog: reject the option without -g
Start preparing for 1.7.12.3
t1450: the order the objects are checked
A release candidate Git v1.8.0-rc0 is now available for testing at
the usual places. There are a couple of leftover features we might
merge before the final release, but other than that, this is meant
to be more or less feature-complete preview of the upcoming 1.8.0.
The release tarballs are
A release candidate Git v1.8.0-rc0 is now available for testing at
the usual places. There are a couple of leftover features we might
merge before the final release, but other than that, this is meant
to be more or less feature-complete preview of the upcoming 1.8.0.
The release tarballs are
tion: fix shell expansion of items"
Jens Lehmann (1):
submodule: use argv_array instead of hand-building arrays
Jeremy White (1):
Documentation: describe subject more precisely
Jonathan "Duke" Leto (1):
Improve the description of GIT_PS1_SHOWUPSTREAM
Junio C
of GIT_PS1_SHOWUPSTREAM
Junio C Hamano (11):
mailinfo: strip RE: prefix
blame $path: avoid getting fooled by case insensitive filesystems
blame: allow blame file in the middle of a conflicted merge
grep: teach --debug option to dump the parse tree
log --grep/--author: honor --all
n on inaccessible attribute files
t5550: put auth-required repo in auth/dumb
t5550: factor out http auth setup
t/lib-httpd: only route auth/dumb to dumb repos
t/lib-httpd: recognize */smart/* repos as smart-http
t: test basic smart-http authentication
t: test http a
: introduce get_max_fd_limit() helper
Junio C Hamano (34):
test: rename $satisfied to $satisfied_prereq
test: allow prerequisite to be evaluated lazily
config: git config baa should exit with status 1
t7406: fix misleading rev-parse --max-count=1 HEAD
sane_execvp(): ignore non
A maintenance release Git v1.7.11.7 is now available at the
usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
30c7aafaa31002ca52bc45dbd0908e63b00015dd git-1.7.11.7.tar.gz
A maintenance release Git v1.7.11.7 is now available at the
usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
30c7aafaa31002ca52bc45dbd0908e63b00015dd git-1.7.11.7.tar.gz
Takashi Iwai writes:
>> I can't reproduce here. What is your exact request-pull invocation?
This question was not answerd. Did you ask request-pull to ask for
a branch to be pulled, or did you ask it to ask for the tag to be
pulled?
If the former, I would have say it is a pebcak. Linus asked
Takashi Iwai ti...@suse.de writes:
I can't reproduce here. What is your exact request-pull invocation?
This question was not answerd. Did you ask request-pull to ask for
a branch to be pulled, or did you ask it to ask for the tag to be
pulled?
If the former, I would have say it is a pebcak.
y self-configuring in the normal case.
Heiko Voigt (2):
Let submodule command exit with error status if path does not exist
Documentation/CodingGuidelines: spell out more shell guidelines
Jay Soffian (1):
gitweb: URL-decode $my_url/$my_uri when stripping PATH_INFO
Jeff King (6):
sha1 as a sentinel value
do not write null sha1s to on-disk index
fsck: detect null sha1 in tree entries
terminal: seek when switching between reading and writing
docs: monospace listings in docbook output
Junio C Hamano (13):
config: git config baa should exit
The latest feature release Git v1.7.12 is now available at the
usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
42ec1037f1ee5bfeb405710c83b73c0515ad26e6 git-1.7.12.tar.gz
The latest feature release Git v1.7.12 is now available at the
usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
42ec1037f1ee5bfeb405710c83b73c0515ad26e6 git-1.7.12.tar.gz
d to access it.
* "git commit --amend" let the user edit the log message and then died
when the human-readable committer name was given insufficiently by
getpwent(3).
----
Changes since v1.7.12-rc2 are as follows:
Ben
nd object flags
Jonathan Nieder (4):
block-sha1: avoid pointer conversion that violates alignment constraints
block-sha1: put expanded macro parameters in parentheses
Makefile: fix location of listing produced by "make subdir/foo.s"
Makefile: BLK_SHA1 does not require
that violates alignment constraints
block-sha1: put expanded macro parameters in parentheses
Makefile: fix location of listing produced by make subdir/foo.s
Makefile: BLK_SHA1 does not require fast htonl() and unaligned loads
Junio C Hamano (4):
mergetool: support --tool-help option
and writing
Jiang Xin (2):
l10n: Update one message in git.pot
l10n: zh_CN.po: update one translation
Junio C Hamano (2):
Git 1.7.11.5
Git 1.7.12-rc3
Matthieu Moy (1):
Documentation: list git-credential in plumbing commands
Peter Baumann (1):
git svn: reset
gettext messages start with dash
rebase: remove obsolete and unused LONG_USAGE which breaks xgettext
i18n: am: mark more strings for translation
Remove dead code which contains bad gettext block
i18n: merge-recursive: mark strings for translation
l10n: Update git.pot (4 n
76 new messages
Johannes Sixt (1):
Makefile: use overridable $(FIND) instead of hard-coded 'find'
Junio C Hamano (3):
Prepare for 1.7.11.5
Drop 1.7.11.x items from 1.7.12 release notes
Git 1.7.12-rc2
Matthieu Moy (1):
git-remote-mediawiki: replace TODO-list
A release candidate Git v1.7.12-rc1 is now available for testing
at the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
34f04ef64fd60bec32388afe27cc4e447ca55229 git-1.7.12.rc1.tar.gz
nges since v1.7.11.3 are as follows:
Jeff King (3):
diff: test precedence of external diff drivers
advice: pass varargs to strbuf_vaddf, not strbuf_addf
commit: document the temporary commit message file
Jens Lehmann (1):
submodules: don't stumble over symbolic links when cloning re
diff drivers
advice: pass varargs to strbuf_vaddf, not strbuf_addf
commit: document the temporary commit message file
Jens Lehmann (1):
submodules: don't stumble over symbolic links when cloning recursively
Junio C Hamano (7):
filter-branch: do not forget the '@' prefix
A release candidate Git v1.7.12-rc1 is now available for testing
at the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
34f04ef64fd60bec32388afe27cc4e447ca55229 git-1.7.12.rc1.tar.gz
Stefan Beller writes:
> +5) "git format-patch HEAD~n"
> +
> +Use "git format-patch HEAD~n" to extract the last n patches from your
> +git repository. They will be be saved in textfiles named
> +
> +0001-Introduce-new-Feature.patch
> +0002-Improve-Documentation.patch
Two comments and a
Stefan Beller stefanbel...@googlemail.com writes:
+5) git format-patch HEAD~n
+
+Use git format-patch HEAD~n to extract the last n patches from your
+git repository. They will be be saved in textfiles named
+
+0001-Introduce-new-Feature.patch
+0002-Improve-Documentation.patch
Two
A release candidate Git v1.7.12-rc0 is now available for testing
at the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
09016e819a69b49090756e9bc5c97a4df25c2f78 git-1.7.12.rc0.tar.gz
A release candidate Git v1.7.12-rc0 is now available for testing
at the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
09016e819a69b49090756e9bc5c97a4df25c2f78 git-1.7.12.rc0.tar.gz
sage with commit --amend
Jay Soffian (1):
fast-export: quote paths with spaces
Jeff King (3):
push: don't guess at qualifying remote refs on deletion
add: create ADD_EDIT.patch with mode 0666
commit: fix "--amend --only" with no pathspec
Junio C Hamano (10):
--only with no pathspec
Junio C Hamano (10):
show: fix range implies walking
t/test-lib.sh: export PERL_PATH for use in scripts
tests: enclose $PERL_PATH in double quotes
t/README: add a bit more Don'ts
diff-index.c: do not pretend paths are pathspecs
diff
Uwe Kleine-König writes:
> It doesn't move it around, that's only how it looks. I removed enum
> mc13xxx_id (above MC13XXX_NUMREGS) and added struct mc13xxx_variant
> (below MC13XXX_NUMREGS). Git choosed to use the closing brace of enum
> mc13xxx_id and struct mc13xxx_variant respectively as
Uwe Kleine-König u.kleine-koe...@pengutronix.de writes:
It doesn't move it around, that's only how it looks. I removed enum
mc13xxx_id (above MC13XXX_NUMREGS) and added struct mc13xxx_variant
(below MC13XXX_NUMREGS). Git choosed to use the closing brace of enum
mc13xxx_id and struct
---
Changes since v1.7.11.1 are as follows:
Carlos Martín Nieto (2):
Documentation: --no-walk is no-op if range is specified
git-cherry-pick.txt: clarify the use of revision range notation
Heiko Voigt (1):
update-index: allow overwriting existing submo
Heiko Voigt (1):
update-index: allow overwriting existing submodule index entries
Jeff King (3):
fix pager.diff with diff --no-index
do not run pager with diff --no-index --quiet
diff: handle relative paths in no-index
Junio C Hamano (15):
request-pull: really favor
rtialness of error message
Documentation/push: clarify matching refspec behavior
push: document the status output
hash: fix lookup_hash semantics
Junio C Hamano (1):
GIT 1.5.4.3
Kristian H淡gsberg (1):
Rename git-core rpm to just git and rename the meta-pacakge to git-all
behavior
push: document the status output
hash: fix lookup_hash semantics
Junio C Hamano (1):
GIT 1.5.4.3
Kristian H淡gsberg (1):
Rename git-core rpm to just git and rename the meta-pacakge to git-all.
Miklos Vajna (1):
Documentation/git-stash: document options
Al Viro <[EMAIL PROTECTED]> writes:
> On Sat, Feb 23, 2008 at 02:37:00AM +0100, Jan Engelhardt wrote:
>
>> >do you tend to clone the entire repository repeatedly into a series
>> >of separate working directories
>>
>> Too time consuming on consumer drives with projects the size of Linux.
>
> git
Al Viro [EMAIL PROTECTED] writes:
On Sat, Feb 23, 2008 at 02:37:00AM +0100, Jan Engelhardt wrote:
do you tend to clone the entire repository repeatedly into a series
of separate working directories
Too time consuming on consumer drives with projects the size of Linux.
git clone -l -s
Linus Torvalds <[EMAIL PROTECTED]> writes:
> So I'd be happier with warnings about deep indentation (but how do you
> count it? Will people then try to fake things out by using 4-space indents
> and then "deep" indentations will look like just a couple of tabs?) and
> against complex
Linus Torvalds [EMAIL PROTECTED] writes:
So I'd be happier with warnings about deep indentation (but how do you
count it? Will people then try to fake things out by using 4-space indents
and then deep indentations will look like just a couple of tabs?) and
against complex expressions (ie
:
bisect: allow starting with a detached HEAD
Document that the default of branch.autosetupmerge is true
bisect: use verbatim commit subject in the bisect log
Johannes Sixt (1):
upload-pack: Initialize the exec-path.
Jonas Fonseca (1):
man pages are littered with .ft
with .ft C and others
Junio C Hamano (31):
git-pull documentation: fix markup
archive-tar.c: guard config parser from value=NULL
Add config_error_nonbool() helper function
builtin-apply.c: guard config parser from value=NULL
builtin-branch.c: guard config parser from
Linus Torvalds <[EMAIL PROTECTED]> writes:
> On Wed, 13 Feb 2008, Linus Torvalds wrote:
>>
>> So in that sense, I think both MAINTAINERS and the deprecation schedule
>> are totally uninteresting. Yes, they have merge conflicts. But those merge
>> conflicts are really really easy to handle.
>
>
Linus Torvalds [EMAIL PROTECTED] writes:
On Wed, 13 Feb 2008, Linus Torvalds wrote:
So in that sense, I think both MAINTAINERS and the deprecation schedule
are totally uninteresting. Yes, they have merge conflicts. But those merge
conflicts are really really easy to handle.
That, btw,
ly when
numeric color values are used.
Changes since v1.5.4 are as follows:
Gerrit Pape (1):
INSTALL: git-merge no longer uses cpio
Jari Aalto (1):
Documentation/git-stash.txt: Adjust SYNOPSIS command syntax (2)
Junio C Hamano (3):
Update
.
Changes since v1.5.4 are as follows:
Gerrit Pape (1):
INSTALL: git-merge no longer uses cpio
Jari Aalto (1):
Documentation/git-stash.txt: Adjust SYNOPSIS command syntax (2)
Junio C Hamano (3):
Update stale documentation links from the main
Linus Torvalds <[EMAIL PROTECTED]> writes:
> On Fri, 8 Feb 2008, Jonathan Corbet wrote:
>> +
>> +These tags are:
>> +
>> +From: The original author of the patch. This tag will ensure
>> +that credit is properly given when somebody other than the
>> +original
Linus Torvalds [EMAIL PROTECTED] writes:
On Fri, 8 Feb 2008, Jonathan Corbet wrote:
+
+These tags are:
+
+From: The original author of the patch. This tag will ensure
+that credit is properly given when somebody other than the
+original author submits
The latest feature release GIT 1.5.4 is available at the usual
places:
http://www.kernel.org/pub/software/scm/git/
git-1.5.4.tar.{gz,bz2}(tarball)
git-htmldocs-1.5.4.tar.{gz,bz2} (preformatted docs)
git-manpages-1.5.4.tar.{gz,bz2}
The latest feature release GIT 1.5.4 is available at the usual
places:
http://www.kernel.org/pub/software/scm/git/
git-1.5.4.tar.{gz,bz2}(tarball)
git-htmldocs-1.5.4.tar.{gz,bz2} (preformatted docs)
git-manpages-1.5.4.tar.{gz,bz2}
breakage in combination with --compose
Jakub Narebski (1):
autoconf: define NO_SYS_SELECT_H on systems without .
Johannes Schindelin (1):
pull --rebase: be cleverer with rebased upstream branches
Junio C Hamano (5):
git-submodule: rename shell functions for consistency
git
breakage in combination with --compose
Jakub Narebski (1):
autoconf: define NO_SYS_SELECT_H on systems without sys/select.h.
Johannes Schindelin (1):
pull --rebase: be cleverer with rebased upstream branches
Junio C Hamano (5):
git-submodule: rename shell functions for consistency
Mathieu Segaud <[EMAIL PROTECTED]> writes:
> Signed-off-by: Mathieu Segaud <[EMAIL PROTECTED]>
> ---
> fs/ext4/dir.c |2 +-
> fs/ext4/file.c |2 +-
> fs/ext4/ioctl.c | 161
> ---
> include/linux/ext4_fs.h |3 +-
Mathieu Segaud [EMAIL PROTECTED] writes:
Signed-off-by: Mathieu Segaud [EMAIL PROTECTED]
---
fs/ext4/dir.c |2 +-
fs/ext4/file.c |2 +-
fs/ext4/ioctl.c | 161
---
include/linux/ext4_fs.h |3 +-
4 files
-clobbered errno value
doc typo: s/prior committing/prior to committing/
Johannes Schindelin (1):
gitk: make Ctrl "+" really increase the font size
Junio C Hamano (8):
builtin-commit.c: remove useless check added by faulty cut and paste
Revert "builtin-commi
to committing/
Johannes Schindelin (1):
gitk: make Ctrl + really increase the font size
Junio C Hamano (8):
builtin-commit.c: remove useless check added by faulty cut and paste
Revert builtin-commit.c: remove useless check added by faulty cut and
paste
Fix git-rerere documentation
Sam Ravnborg <[EMAIL PROTECTED]> writes:
> I wonder how these tabs came in.
> I am almost sure they were not in my original patch. But as git-send-email
> do not save copies of my sent mails I cannot be sure.
>
> Ingo - do you have a script on your side that could have converted
> the spaces to
Sam Ravnborg [EMAIL PROTECTED] writes:
I wonder how these tabs came in.
I am almost sure they were not in my original patch. But as git-send-email
do not save copies of my sent mails I cannot be sure.
Ingo - do you have a script on your side that could have converted
the spaces to tabs?
It
Ismail Dönmez <[EMAIL PROTECTED]> writes:
> Saturday 12 January 2008 09:11:23 tarihinde Junio C Hamano şunları yazmıştı:
>> The third rc for the next feature release GIT 1.5.4 is available
>> at the usual places:
>>
>> http://www.kernel.org/pub/software/scm/g
undle, fast-import: detect write failure
Johannes Schindelin (2):
Optimize prefixcmp()
shortlog: mention the "-e" option in the usage
Johannes Sixt (2):
git-gui: Move frequently used commands to the top of the context menu.
recv_sideband: Do not use ANSI esca
Schindelin (2):
Optimize prefixcmp()
shortlog: mention the -e option in the usage
Johannes Sixt (2):
git-gui: Move frequently used commands to the top of the context menu.
recv_sideband: Do not use ANSI escape sequence on dumb terminals.
Junio C Hamano (27
Ismail Dönmez [EMAIL PROTECTED] writes:
Saturday 12 January 2008 09:11:23 tarihinde Junio C Hamano şunları yazmıştı:
The third rc for the next feature release GIT 1.5.4 is available
at the usual places:
http://www.kernel.org/pub/software/scm/git/
git-1.5.4.rc3.tar.{gz,bz2
Andi Kleen <[EMAIL PROTECTED]> writes:
> I imagined it would check for
>
> +struct file_operations ... = {
> + ...
> + .ioctl = ...
>
> That wouldn't catch the case of someone adding only .ioctl to an
> already existing file_operations which is not visible in the patch context,
> but
Andi Kleen [EMAIL PROTECTED] writes:
I imagined it would check for
+struct file_operations ... = {
+ ...
+ .ioctl = ...
That wouldn't catch the case of someone adding only .ioctl to an
already existing file_operations which is not visible in the patch context,
but that
rking tree
clone: correctly report http_fetch errors
git-send-email: avoid duplicate message-ids
Jim Meyering (1):
config.c:store_write_pair(): don't read the byte before a
malloc'd buffer.
Junio C Hamano (3):
git grep shows the same hit repeatedly for unmerged paths
clone: correctly report http_fetch errors
git-send-email: avoid duplicate message-ids
Jim Meyering (1):
config.c:store_write_pair(): don't read the byte before a
malloc'd buffer.
Junio C Hamano (3):
git grep shows the same hit repeatedly for unmerged paths
git-am
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
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 the .git/refs/tags/
Linus Torvalds <[EMAIL PROTECTED]> writes:
> Actually, the code to finding one '\n' is still needed to avoid the
> (pathological) case of getting a "\No newline", so scrap that one which
> was too aggressive, and use this (simpler) one instead.
>
> Not that it matters in real life, since nobody
Linus Torvalds [EMAIL PROTECTED] writes:
Actually, the code to finding one '\n' is still needed to avoid the
(pathological) case of getting a \No newline, so scrap that one which
was too aggressive, and use this (simpler) one instead.
Not that it matters in real life, since nobody uses
Divy Le Ray <[EMAIL PROTECTED]> writes:
> On this topic, I have a question: how do I get to see all the
> netdev-2.6 branches ?
> After cloning a free netdev-2.6 tree, 'git branch' shows only the
> master branch:
> ...
> Cloning
>
Divy Le Ray [EMAIL PROTECTED] writes:
On this topic, I have a question: how do I get to see all the
netdev-2.6 branches ?
After cloning a free netdev-2.6 tree, 'git branch' shows only the
master branch:
...
Cloning
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
into
dle create: keep symbolic refs' names instead of resolving them
Replace the word 'update-cache' by 'update-index' everywhere
Johannes Sixt (1):
t7003-filter-branch: Fix test of a failing --msg-filter.
Junio C Hamano (11):
format-patch -s: add MIME encoding header if signer's n
-filter-branch: Fix test of a failing --msg-filter.
Junio C Hamano (11):
format-patch -s: add MIME encoding header if signer's name requires so
test format-patch -s: make sure MIME content type is shown as needed
ce_match_stat, run_diff_files: use symbolic constants for readability
b: Minor cleanups and fixes for potential problems
Documentation: Fix man page breakage with DocBook XSL v1.72
Jonathan del Strother (1):
Fixing path quoting in git-rebase
Junio C Hamano (12):
grep with unmerged index
refresh_index_quietly(): express "optional" nature of index
man page breakage with DocBook XSL v1.72
Jonathan del Strother (1):
Fixing path quoting in git-rebase
Junio C Hamano (12):
grep with unmerged index
refresh_index_quietly(): express optional nature of index writing better
Makefile: add missing dependency on wt-status.h
m Tjernlund (1):
Improve receive-pack error message about funny ref creation
Johannes Schindelin (5):
clear_commit_marks(): avoid deep recursion
rebase -i: use diff plumbing instead of porcelain
Fix setup_git_directory_gently() with relative GIT_DIR & GIT_WORK_TREE
: update current branch when rewritten
Julian Phillips (1):
fast-import: Fix argument order to die in file_change_m
Junio C Hamano (8):
git-remote: fix Use of uninitialized value in string ne
sha1_file.c: avoid gcc signed overflow warnings
merge-recursive.c: mrtree in merge
Jan Engelhardt <[EMAIL PROTECTED]> writes:
> On Oct 30 2007 12:31, Linus Torvalds wrote:
>>On Tue, 30 Oct 2007, Jeff Garzik wrote:
>>>
>>> Can we change git-am to accept two dashes as well as three? :)
>>
>>Well, git-am actually used to be a lot less strict about the dashes, and
>>we've made
601 - 700 of 857 matches
Mail list logo
