On Sun, Dec 22, 2013 at 1:38 PM, Junio C Hamano gits...@pobox.com wrote:
Duy Nguyen pclo...@gmail.com writes:
I am not happy with the choice of main/HEAD that would squat on a
good name for remote-tracking branch (i.e. s/origin/main/), though.
$GIT_DIR/COMMON_HEAD perhaps?
It's not just
On Sat, Dec 14, 2013 at 3:43 AM, Jonathan Nieder jrnie...@gmail.com wrote:
Problems:
* What if I move my worktree with mv? Then I still need the
corresponding $GIT_SUPER_DIR/repos/id directory, and nobody told
the GIT_SUPER_DIR about it.
* What if my worktree is on removable media
On Tue, Dec 24, 2013 at 12:48 AM, Torsten Bögershausen tbo...@web.de wrote:
+test_expect_success 'git add -A on empty repo does not error out' '
+ git init empty ( cd empty git add -A . )
+'
+
test_done
I am (a little bit) confused.
This is what git does:
rm -rf test mkdir test
On Wed, Dec 25, 2013 at 4:48 AM, Torsten Bögershausen tbo...@web.de wrote:
On 2013-12-24 00.46, Duy Nguyen wrote:
[snip]
We don't complain about adding an empty directory before or after this patch.
Ok, thanks for the explanation.
I think that
https://www.kernel.org/pub/software/scm/git
On Fri, Dec 27, 2013 at 12:12 AM, Junio C Hamano gits...@pobox.com wrote:
Duy Nguyen pclo...@gmail.com writes:
On Sun, Dec 22, 2013 at 1:38 PM, Junio C Hamano gits...@pobox.com wrote:
Do we even need to expose them as ref-like things as a part of the
external API/UI in the first place
On Tue, Dec 31, 2013 at 7:07 PM, Kyle J. McKay mack...@gmail.com wrote:
Since 64a99eb4 git gc refuses to run without the --force option if
another gc process on the same repository is already running.
However, if the repository is shared and user A runs git gc on the
repository and while that
On Mon, Jan 6, 2014 at 7:00 AM, Ramsay Jones ram...@ramsay1.demon.co.uk wrote:
Commit 58babfff (shallow.c: the 8 steps to select new commits for
.git/shallow, 05-12-2013) added a function to implement step 5 of
the quoted eight steps, namely 'remove_nonexistent_ours_in_pack()'.
This function
On Tue, Jan 14, 2014 at 12:02 AM, Jonathan Nieder jrnie...@gmail.com wrote:
Hi,
Nguyễn Thái Ngọc Duy wrote:
If an entry is watched, git lets an external program decide if the
entry is modified or not. It's more like --assume-unchanged, but
designed to be controlled by machine.
We are
On Sun, Jan 12, 2014 at 6:03 PM, Nguyễn Thái Ngọc Duy pclo...@gmail.com wrote:
We are running out of on-disk ce_flags,
Correction, we're not. I saw
/*
* Extended on-disk flags
*/
#define CE_INTENT_TO_ADD (1 29)
#define CE_SKIP_WORKTREE (1 30)
followed by
/* CE_EXTENDED2 is for
On Wed, Jan 15, 2014 at 1:44 AM, Martin Langhoff
martin.langh...@gmail.com wrote:
Diagnosing errors with git over ssh has historically required tooling
up for debugging or looking at things from the client side, because
git does not log anything on the server side.
It would be a boon to those
On Thu, Jan 9, 2014 at 10:05 PM, Mathieu Lemoine math...@mlemoine.name wrote:
Hello,
In https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.5.txt
is mentioned:
* Instead of typing four capital letters HEAD, you can say @ now,
e.g. git log @.
However, `git symbolic-ref @`
On Thu, Jan 16, 2014 at 6:50 AM, Martin Langhoff
martin.langh...@gmail.com wrote:
On Wed, Jan 15, 2014 at 12:49 PM, Junio C Hamano gits...@pobox.com wrote:
As long as we can reliably determine that it is safe to do so
without risking races, automatically cleaning .lock files is a good
thing to
On Fri, Jan 17, 2014 at 5:43 AM, Jonathan Nieder jrnie...@gmail.com wrote:
Subject: gitignore doc: add global gitignore to synopsis
The gitignore(5) manpage already documents $XDG_CONFIG_HOME/git/ignore
but it is easy to forget that it exists. Add a reminder to the
synopsis.
Yes! I knew
On Fri, Jan 17, 2014 at 10:24 PM, Torsten Bögershausen tbo...@web.de wrote:
On 2014-01-17 10.47, Nguyễn Thái Ngọc Duy wrote:
[snip[
diff --git a/file-watcher-lib.c b/file-watcher-lib.c
+int connect_watcher(const char *path)
Could it be worth to check if we can use some code from
On Mon, Jan 20, 2014 at 12:04 AM, Thomas Rast t...@thomasrast.ch wrote:
I never got the last three patches, did you send them?
Also, this doesn't cleanly apply anywhere at my end. Can you push it
somewhere for easier experimentation?
Sorry I rebased it on top of kb/fast-hashmap but never got
On Mon, Jan 20, 2014 at 12:04 AM, Thomas Rast t...@thomasrast.ch wrote:
Nguyễn Thái Ngọc Duy pclo...@gmail.com writes:
This can be used to force watcher on when running the test
suite.
git-file-watcher processes are not automatically cleaned up after each
test. So after running the test
On Mon, Jan 20, 2014 at 12:06 AM, Thomas Rast t...@thomasrast.ch wrote:
Nguyễn Thái Ngọc Duy pclo...@gmail.com writes:
watch_entries() is a lot of computation and could trigger a lot more
lookups in file-watcher. Normally after the first set of watches are
in place, we do not need to update
On Mon, Jan 20, 2014 at 12:06 AM, Thomas Rast t...@thomasrast.ch wrote:
Nguyễn Thái Ngọc Duy pclo...@gmail.com writes:
If an entry is watched, git lets an external program decide if the
entry is modified or not. It's more like --assume-unchanged, but
designed to be controlled by machine.
We
On Tue, Jan 21, 2014 at 4:32 AM, Jeff King p...@peff.net wrote:
This patch therefore ties the extra tree examination to the
revs-edge_hint flag; it is the presence of that flag that
makes the tradeoff worthwhile.
Here is output from the p0001-rev-list showing the
improvement in performance:
On Wed, Jan 22, 2014 at 6:22 PM, Michael Haggerty mhag...@alum.mit.edu wrote:
These sections are inconsistent with the other manpages and seem
superfluous in a project that has, on the one hand, a public history
and, on the other hand, hundreds of contributors. Would the mentioned
authors
On Thu, Jan 23, 2014 at 3:35 AM, Jens Lehmann jens.lehm...@web.de wrote:
Am 20.01.2014 19:25, schrieb Paweł Sikora:
i've noticed that 'git log submodule-dir' and 'git log submodule-dir/'
return different results (module's head changes vs. nothing). is it a bug?
looks like a trailing slash is a
On Fri, Jan 24, 2014 at 4:38 AM, Junio C Hamano gits...@pobox.com wrote:
Jens Lehmann jens.lehm...@web.de writes:
... But a single
trailing '/' does mark submod as a directory, which I think is
ok for a submodule. And it makes life easier for the user if we
accept that, as shell completion
On Sat, Jan 25, 2014 at 2:22 AM, Junio C Hamano gits...@pobox.com wrote:
How does git status '[b]/' behave?
It outputs b/ (like git status b). I think that's because
common_prefix_len() stops looking at the first wildcard char, '['. So
common prefix is empty, just like b.
--
Duy
--
To
On Thu, Jan 23, 2014 at 11:45:25AM +0900, IWAMOTO Toshihiro wrote:
I found git-diff --quiet returns a zero exit status even if there's
a change. The following sequence reproduces the bug:
$ mkdir foo
$ cd foo
$ git init
$ echo a a.txt
$ echo b b.txt
$ git add ?.txt
$ git
On Sat, Jan 25, 2014 at 10:34 AM, Yuri y...@rawbw.com wrote:
The fragment of 'git diff' output looks like this:
- translationОшибка: адрес %1 содержит запрещенные символы. Пожалуйста,
перепро�
+ translationОшибка: адрес %1 содержит запрещённые символы. Пожалуйста,
перепро�
Two issues here:
On Sat, Jan 25, 2014 at 4:22 AM, Eric Sunshine sunsh...@sunshineco.com wrote:
On Fri, Jan 24, 2014 at 8:40 AM, Nguyễn Thái Ngọc Duy pclo...@gmail.com
wrote:
diff --git a/t/t4010-diff-pathspec.sh b/t/t4010-diff-pathspec.sh
index af5134b..167af53 100755
--- a/t/t4010-diff-pathspec.sh
+++
On Sat, Jan 25, 2014 at 10:06:46PM +, Andy Spencer wrote:
The current basedir compare aborts early in order to avoid futile
recursive searches. However, a match may still be found by another
pathspec. This can cause an error while checking out files from a branch
when using multiple
On Mon, Jan 27, 2014 at 7:07 AM, Martin Erik Werner
martinerikwer...@gmail.com wrote:
diff --git a/setup.c b/setup.c
index 5432a31..0789a96 100644
--- a/setup.c
+++ b/setup.c
@@ -22,11 +22,51 @@ char *prefix_path_gently(const char *prefix, int len,
const char *orig = path;
On Mon, Jan 27, 2014 at 4:10 AM, Joe Perches j...@perches.com wrote:
For instance (using the Linus' linux kernel git):
$ time git log --follow -- drivers/firmware/google/Kconfig /dev/null
real0m42.329s
user0m40.984s
sys 0m0.792s
$ time git blame --
On Mon, Jan 27, 2014 at 4:10 AM, Joe Perches j...@perches.com wrote:
Is there something that can be done about improving
git log --follow -- file performance to be nearly
equivalent speed to git blame -- file ?
Not strictly about --follow, but there is room for improvement for
diff'ing in log
On Mon, Jan 27, 2014 at 7:45 PM, David Kastrup d...@gnu.org wrote:
The git blame manual page talks about using git blame --reverse to
figure out when a particular change disappeared, but I cannot make it
produce anything useful regardless of what range I give it. Using
--root delivers a
On Mon, Jan 20, 2014 at 12:04 AM, Thomas Rast t...@thomasrast.ch wrote:
There's also the problem of ordering guarantees between the socket and
inotify. I haven't found any, so I would conservatively assume that the
socket messages may in fact arrive before inotify, which is a race in
the
On Tue, Jan 28, 2014 at 02:51:45PM -0800, Junio C Hamano wrote:
This replaces 'diff: turn off skip_stat_unmatch on diff --cached'
The previous patch obviously leaves skip_stat_unmatch on in diff
rev rev and maybe other cases.
Oops, I lost track. Sorry.
Together with {1,2}/3
Just a quick update for the enthusiasts. My branch file-watcher [1]
has got working per-user inotify support. It's a 20 patch series so
I'll refrain from spamming git@vger for a while, even though it hurts
your eyes a lot less than what I have posted so far. The test suite
ran fine with it so it's
On Wed, Jan 29, 2014 at 2:44 PM, Mike Hommey m...@glandium.org wrote:
Haven't looked at the code, so I don't know if you've done that, but in
case you haven't, it would be nice to have an environment variable or a
config option to make git use the file-watcher *and* normal lstat
operations, to
On Sat, Feb 1, 2014 at 3:22 AM, Martin Erik Werner
martinerikwer...@gmail.com wrote:
diff --git a/setup.c b/setup.c
index 5432a31..e606846 100644
--- a/setup.c
+++ b/setup.c
@@ -77,6 +77,69 @@ int path_inside_repo(const char *prefix, const char *path)
return 0;
}
+/*
+ * It is
I usually start splitting a commit with reset @^ then add -p back.
The problem is reset @^ does not keep track of new files added in
HEAD, so I often end up forgetting to add new files back (with add
-p). I'm thinking of making reset to do add -N automatically for
me so I won't miss changes in add
On Sun, Feb 2, 2014 at 8:59 AM, Martin Erik Werner
martinerikwer...@gmail.com wrote:
+ /* check if work tree is already the prefix */
+ if (strncmp(path, work_tree, wtlen) == 0) {
+ if (path[wtlen] == '/')
+ memmove(path, path + wtlen + 1, len -
On Sun, Feb 2, 2014 at 9:19 AM, Duy Nguyen pclo...@gmail.com wrote:
+ /* check whole path */
+ if (strcmp(real_path(path0), work_tree) == 0) {
+ *path0 = '\0';
+ return 0;
+ }
I think this is already handled by the check if work tree is already
On Sun, Feb 2, 2014 at 5:37 PM, David Kastrup d...@gnu.org wrote:
in the context of an ongoing discussion on the Emacs developer list of
converting the Bzr repository of Emacs, one question (with different
approaches) is where to put the information regarding preexisting Bazaar
revision
On Sun, Feb 2, 2014 at 6:19 PM, David Kastrup d...@gnu.org wrote:
Since Git has a working facility for references that is catered to do
exactly this kind of mapping and already _does_, it seems like a
convenient path to explore.
It will not scale. If you make those refs available for
On Sun, Feb 2, 2014 at 6:13 PM, Martin Erik Werner
martinerikwer...@gmail.com wrote:
diff --git a/setup.c b/setup.c
index 2270bd4..5817875 100644
--- a/setup.c
+++ b/setup.c
@@ -32,9 +32,11 @@ static inline int abspath_part_inside_repo(char *path)
if (strncmp(path, work_tree, wtlen)
;. But it's
not a big deal imo. The rest of the series looks good.
Reviewed-by: Duy Nguyen pclo...@gmail.com
} else {
sanitized = xmalloc(len + strlen(path) + 1);
if (len)
--
Duy
--
To unsubscribe from this list: send the line unsubscribe git in
the body
On Tue, Feb 4, 2014 at 2:54 AM, Jens Lehmann jens.lehm...@web.de wrote:
Implement the functionality needed to enable work tree manipulating
commands so that an changed submodule does not only affect the index but
it also updates the work tree of any initialized submodule according to
the SHA-1
On Tue, Feb 4, 2014 at 1:11 AM, Junio C Hamano gits...@pobox.com wrote:
Jeff King p...@peff.net writes:
[1] I _do_ use reset -p when splitting commits, but I do not think it
is useful here. I use it for oops, I staged this change, but it
actually belongs in the next commit. Undo my
On Tue, Feb 4, 2014 at 9:20 AM, chris j...@hotmail.com wrote:
$ git push origin next
Counting objects: 56, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (9/9), done.
Writing objects: 100% (9/9), 895 bytes | 0 bytes/s, done.
Total 9 (delta 8), reused 0 (delta 0)
On Tue, Feb 4, 2014 at 12:13 PM, chris j...@hotmail.com wrote:
However, I question why I should even care about this message? I'm going to
assume that simply it is a lengthy synchronous operation that someone felt
deserved some verbosity to why the client push action is taking longer than
it
On Tue, Feb 04, 2014 at 02:25:25PM -0800, Junio C Hamano wrote:
Junio C Hamano gits...@pobox.com writes:
While I do not have any problem with adding an optional keep lost
paths as intent-to-add entries feature, I am not sure why this has
to be so different from the usual add-cache-entry
On Thu, Feb 6, 2014 at 1:25 AM, Junio C Hamano gits...@pobox.com wrote:
Yes, indeed. I wonder why your new test did not notice it, though
;-)
... and the answer turns out to be that it was not testing the right
thing. On top of that faulty version, this will fix it.
Yes, write-tree should
On Tue, Feb 4, 2014 at 11:05 PM, Jonathan Nieder jrnie...@gmail.com wrote:
t/t7101-reset-empty-subdirs.sh (new +x) | 63
+
t/t7101-reset.sh (gone) | 63
-
t/t7104-reset-hard.sh (new +x) | 46
On Wed, Feb 5, 2014 at 1:55 PM, Michael Haggerty mhag...@alum.mit.edu wrote:
* Duy seemed to offer to rewrite his patch series, but I don't think
that it has happened yet.
It's really low in my todo list. So if you want to pick it up, please do.
--
Duy
--
To unsubscribe from this list: send
(Digging back an old topic after Jeff mentioned it)
On Thu, May 9, 2013 at 2:12 AM, Junio C Hamano gits...@pobox.com wrote:
Jeff King p...@peff.net writes:
I'm trying to track down a protocol bug that happens with shallow clones
over smart-http. As far as I can tell, the bug has existed in
On Thu, Feb 6, 2014 at 8:20 PM, Johannes Sixt j.s...@viscovery.net wrote:
Am 2/6/2014 12:54, schrieb konst...@ngs.ru:
However I typed the checkout directory in file
..git/info/sparse-checkout by using different formats with
and without the leading and the trailing slashes, with and
without
On Fri, Feb 7, 2014 at 2:31 AM, Junio C Hamano gits...@pobox.com wrote:
Nguyễn Thái Ngọc Duy pclo...@gmail.com writes:
Reported by Jeff [1]. Junio spotted it right but nobody made any move
since then.
Hrm. Was I supposed to make any move at that point? The discussion
ended by me asking a
On Fri, Feb 7, 2014 at 2:16 AM, Junio C Hamano gits...@pobox.com wrote:
Nguyễn Thái Ngọc Duy pclo...@gmail.com writes:
In smart http, upload-pack adds new shallow lines at the beginning of
each rpc response. Only shallow lines from the first rpc call are
useful. After that they are thrown
On Fri, Feb 07, 2014 at 09:43:46AM +, Francis Stephens wrote:
Thanks for your clear response. I can see where I went wrong now.
Maybe something like this would help avoid confusion a bit in the
future? This toy patch puts a horizontal line as a break between two
commits if they are not
On Fri, Feb 7, 2014 at 7:36 PM, chris j...@hotmail.com wrote:
Junio C Hamano gitster at pobox.com writes:
Instead of adding a boolean --break-ok that is hidden, why not
adding an exposed boolean --daemonize, and let auto-gc run in the
background? With the recent do not let more than one gc
On Fri, Feb 07, 2014 at 10:01:08AM -0800, Junio C Hamano wrote:
Here is the difference between the posted series and what I queued
after applying the changes suggested during the review.
Thanks.
I was going to send a reroll after the received comments. Could you
put this on top of 6/6, just
(Dropped some CC as this becomes a different topic)
On Sat, Feb 8, 2014 at 2:20 AM, Jonathan Nieder jrnie...@gmail.com wrote:
Duy Nguyen wrote:
Don't take it the wrong way. I was just summarizing the last round. It
surprised me though that this went under my radar. Perhaps a bug
tracker
On Sat, Feb 8, 2014 at 6:47 AM, Jeff King p...@peff.net wrote:
Thinking on this more, I wonder if we should just do something like
this:
diff --git a/t/lib-httpd.sh b/t/lib-httpd.sh
index bfdff2a..c82b4ee 100644
--- a/t/lib-httpd.sh
+++ b/t/lib-httpd.sh
@@ -64,7 +64,9 @@ case $(uname) in
Thanks for the comments. I can see I now have some work to do in the
coming weeks :)
On Sat, Feb 8, 2014 at 3:04 PM, Torsten Bögershausen tbo...@web.de wrote:
I would appreciate if we could have an outline of the protocol
as a seperate document somewhere, to be able to have a look at the
On Fri, Dec 20, 2013 at 3:50 AM, Jonathan Nieder jrnie...@gmail.com wrote:
Junio C Hamano wrote:
Jonathan Nieder jrnie...@gmail.com writes:
This includes the colon in the translated string, to make it easier to
remember to keep the non-breaking space before it.
Hmph, recent 3651e45c
On Sat, Feb 8, 2014 at 11:45 PM, Jeff King p...@peff.net wrote:
On Sat, Feb 08, 2014 at 03:10:02PM +0700, Nguyễn Thái Ngọc Duy wrote:
Trailing spaces are invisible in most standard editors (*). git diff
does show trailing spaces by default. But that does not help newly
written .gitignore
On Tue, Feb 04, 2014 at 11:20:39AM +0100, Daniel Hahler wrote:
Hi,
when using a submodule sm, there is a relative worktree in its config:
.git/modules/sm/config:
[core]
worktree = ../../../smworktree
git-new-worktree (from contrib) symlinks this config the new worktree.
On Mon, Feb 10, 2014 at 11:07 AM, Junio C Hamano gits...@pobox.com wrote:
Nguyễn Thái Ngọc Duy pclo...@gmail.com writes:
Trailing spaces are invisible in most standard editors (*). git diff
does show trailing spaces by default. But that does not help newly
written .gitignore files. And
On Mon, Feb 10, 2014 at 3:19 AM, Torsten Bögershausen tbo...@web.de wrote:
Please see filewatcher.c:
+ if (daemon) {
+ int err;
+ strbuf_addf(sb, %s/log, socket_path);
+ err = open(sb.buf, O_CREAT | O_TRUNC | O_WRONLY, 0600);
+
On Mon, Feb 10, 2014 at 6:03 PM, Erik Faye-Lund kusmab...@gmail.com wrote:
`gc --auto` takes time and can block the user temporarily (but not any
- if (!quiet)
- fprintf(stderr,
- _(Auto packing the repository for
On Tue, Feb 11, 2014 at 1:46 AM, Junio C Hamano gits...@pobox.com wrote:
Nguyễn Thái Ngọc Duy pclo...@gmail.com writes:
diff --git a/setup.c b/setup.c
index 6c3f85f..b09a412 100644
--- a/setup.c
+++ b/setup.c
@@ -787,3 +787,27 @@ void sanitize_stdfds(void)
if (fd 2)
On Mon, Feb 10, 2014 at 11:55 PM, Torsten Bögershausen tbo...@web.de wrote:
On 2014-02-10 11.37, Duy Nguyen wrote:
Could we use relative path names internally, relative to $GIT_DIR ?
No because this is when the client tell the server about $GIT_DIR. I
guess we can use realpath(1) here.
Good
On Tue, Feb 11, 2014 at 6:17 PM, David Kastrup d...@gnu.org wrote:
Looking in the Makefile, I just find support for coverage reports using
gcov. Whatever is there with profile in it seems to be for
profile-based compilation rather than using gprof.
Now since I've managed to push most of the
On Tue, Feb 11, 2014 at 2:11 AM, Junio C Hamano gits...@pobox.com wrote:
On Mon, Feb 10, 2014 at 10:43 AM, Junio C Hamano gits...@pobox.com wrote:
If --quiet is set, we should not be printing anyway. If not, I thinkg
we could only print auto packing in background.. when we actually
can do
On Wed, Feb 12, 2014 at 8:54 AM, Stefan Zager sza...@chromium.org wrote:
We in the chromium project have a keen interest in adding threading to
git in the pursuit of performance for lengthy operations (checkout,
status, blame, ...). Our motivation comes from hitting some
performance walls
On Wed, Feb 12, 2014 at 9:02 AM, Robin H. Johnson robb...@gentoo.org wrote:
On Tue, Feb 11, 2014 at 05:54:51PM -0800, Stefan Zager wrote:
We in the chromium project have a keen interest in adding threading to
git in the pursuit of performance for lengthy operations (checkout,
status, blame,
On Wed, Feb 12, 2014 at 8:23 PM, David Kastrup d...@gnu.org wrote:
Johannes Sixt j.s...@viscovery.net writes:
Am 2/12/2014 13:55, schrieb David Kastrup:
Johannes Sixt j.s...@viscovery.net writes:
Running test suite of 'next' on Windows fails in t5310-pack-bitmaps with
the following
On Thu, Feb 13, 2014 at 5:12 AM, Jeff King p...@peff.net wrote:
lib-httpd was never designed to be included from anywhere except the
beginning of the file. But that wouldn't be right for t5537, because it
wants to run some of the tests, even if apache setup fails. The right
way to do it is
On Fri, Feb 14, 2014 at 7:45 PM, Andreas Schwab sch...@linux-m68k.org wrote:
Josef Wolf j...@raven.inka.de writes:
Notice the refs/heads _within_ refs/heads!
Now I wonder how I managed to get into this situation and what's the best way
to recover?
Probably you did something like git branch
On Sat, Feb 15, 2014 at 2:16 AM, Zachary Turner ztur...@chromium.org wrote:
(Gah, sorry if you're receiving multiple emails to your personal
addresses, I need to get used to manually setting Plain-text mode
every time I send a message).
For the mixed read, we wouldn't be looking for another
On Sat, Feb 15, 2014 at 7:50 AM, Stefan Zager sza...@google.com wrote:
On Fri, Feb 14, 2014 at 4:45 PM, Duy Nguyen pclo...@gmail.com wrote:
On Sat, Feb 15, 2014 at 2:16 AM, Zachary Turner ztur...@chromium.org wrote:
(Gah, sorry if you're receiving multiple emails to your personal
addresses, I
On Sat, Feb 15, 2014 at 8:15 AM, Zachary Turner ztur...@chromium.org wrote:
Even if we make that change to use TLS for this case, the
implementation of pread() will still change in such a way that the
semantics of pread() are different on Windows. Is that ok?
Just to summarize, here's the
On Sat, Feb 15, 2014 at 3:23 PM, David Kastrup d...@gnu.org wrote:
Nguyễn Thái Ngọc Duy pclo...@gmail.com writes:
Long story short, we wanted globbing wildcard ** so I ripped
wildmatch library from rsync to do it.
Since version 3.0.0, rsync is GPLv3
URL:https://rsync.samba.org/GPL.html. So
On Fri, Feb 14, 2014 at 08:32:07AM -0800, Junio C Hamano wrote:
Duy Nguyen pclo...@gmail.com writes:
On Fri, Feb 14, 2014 at 7:45 PM, Andreas Schwab sch...@linux-m68k.org
wrote:
Josef Wolf j...@raven.inka.de writes:
Notice the refs/heads _within_ refs/heads!
Now I wonder how I
On Sat, Feb 15, 2014 at 4:14 PM, Nguyễn Thái Ngọc Duy pclo...@gmail.com wrote:
--mixed does mainly two things: read_from_tree(), which does not
require a worktree, and refresh_index(), which does.
.. and I should have run the entire test suite before sending this. It
breaks t7103.5 (reset
On Sat, Feb 15, 2014 at 7:17 PM, Thomas Rast t...@thomasrast.ch wrote:
It also includes an ok from Nicolas Pitre, who has been the driving
force behind packv5 development. The only thing that makes me uneasy is
Nit: pack v4. You are probably confused with index v5, which is also
cooking for a
On Sun, Feb 16, 2014 at 2:23 AM, Thomas Gummerer t.gumme...@gmail.com wrote:
Hi,
since index-v5 didn't seem to generate enough interest to be merged, I
I thought there were some comments last time that you were going to
address and resubmit?
have a few patches that give users users easier
On Sun, Feb 9, 2014 at 2:03 AM, Thomas Rast t...@thomasrast.ch wrote:
Easy:
* Add -p 'e' when it fails to apply should offer an obvious way of
starting from the original hunk (not the broken one) or both
If it's too easy, you can add a command to change diff display
settings (--color-words,
On Mon, Feb 17, 2014 at 3:34 AM, Ingo Rohloff lund...@gmx.de wrote:
Hello,
while trying out git (version 1.7.9.5), I did this:
git clone -- ssh://myserver/~rohloff/git/w1.git w1
So I just cloned a test repository.
The in the cloned w1 repository I executed:
git branch origin/master
git
On Mon, Feb 17, 2014 at 4:36 PM, Daniel Hahler
genml+git-2...@thequod.de wrote:
On 09.02.2014 10:08, Duy Nguyen wrote:
On Tue, Feb 04, 2014 at 11:20:39AM +0100, Daniel Hahler wrote:
Thanks for looking into this.
when using a submodule sm, there is a relative worktree in its config:
.git
On Mon, Feb 10, 2014 at 3:19 AM, Torsten Bögershausen tbo...@web.de wrote:
On 2014-02-08 09.53, Duy Nguyen wrote:
file-watcher.c | 32
1 file changed, 32 insertions(+)
I feel a little bit unsure about the 700.
Most often Git does not care about permissions
On Tue, Feb 18, 2014 at 3:55 PM, David Kastrup d...@gnu.org wrote:
Christian Jaeger chr...@gmail.com writes:
I've got a repository where git log --raw _somefile took a few
seconds in the past, but after an attempt at merging some commits that
were collected in a clone of the same repo that
On Wed, Feb 19, 2014 at 3:59 AM, Junio C Hamano gits...@pobox.com wrote:
Let's do something like this first and then later make --depth
configurable just like --width, perhaps? For aggressive, I think
the default width (hardcoded to 250 but configurable) is a bit too
narrow.
builtin/gc.c |
On Tue, Feb 18, 2014 at 9:46 PM, Johan Herland jo...@herland.net wrote:
On Mon, Feb 17, 2014 at 11:48 AM, yann.dir...@bertin.fr wrote:
The recent git-note -C changes commit type? thread
(http://thread.gmane.org/gmane.comp.version-control.git/241950) looks
like a good occasion to discuss
On Wed, Feb 19, 2014 at 7:10 AM, Junio C Hamano gits...@pobox.com wrote:
Duy Nguyen pclo...@gmail.com writes:
Lower depth than default (50) does not sound aggressive to me, at
least from disk space utilization. I agree it should be configurable
though.
Do you mean you want to keep
On Wed, Feb 19, 2014 at 3:38 PM, Philippe Vaucher
philippe.vauc...@gmail.com wrote:
fwiw this is the thread that added --depth=250
http://thread.gmane.org/gmane.comp.gcc.devel/94565/focus=94626
This post is quite interesting:
http://article.gmane.org/gmane.comp.gcc.devel/94637
Especially
On Wed, Feb 19, 2014 at 4:01 PM, David Kastrup d...@gnu.org wrote:
Calling git blame via C-x v g is a rather important part of the
workflow, and it's currently intolerable to work with on a number of
files.
While I'm fixing the basic shortcomings in builtin/blame.c itself, the
operation
On Wed, Feb 19, 2014 at 9:09 PM, Jeff King p...@peff.net wrote:
On Wed, Feb 19, 2014 at 08:39:27PM +0700, Nguyễn Thái Ngọc Duy wrote:
--sort=version sorts tags as versions. GNU extension's strverscmp is
used and no real compat implementation is provided so this is Linux only.
Sounds like a
On Thu, Feb 20, 2014 at 3:35 AM, Shawn Pearce spea...@spearce.org wrote:
Why a new daemon? Why don't we reuse the stable
https://github.com/facebook/watchman project Facebook built to make
Hg's status system fast?
I did look briefly through its readme before but there were a few
off-factors
On Thu, Feb 20, 2014 at 6:48 AM, Junio C Hamano gits...@pobox.com wrote:
Nguyễn Thái Ngọc Duy pclo...@gmail.com writes:
@@ -651,14 +653,10 @@ static void update_refs_for_switch(const struct
checkout_opts *opts,
new-name);
}
On Thu, Feb 20, 2014 at 10:41 AM, Junio C Hamano gits...@pobox.com wrote:
Duy Nguyen pclo...@gmail.com writes:
- }
+ if (old-path old-name
+ !file_exists(git_path(%s, old-path))
+ file_exists(git_path(logs/%s, old-path
On Thu, Feb 20, 2014 at 3:17 AM, Junio C Hamano gits...@pobox.com wrote:
+ strbuf_setlen(sb, len);
+ strbuf_add(sb, s, strlen(s));
I am not sure addstr_at() gives us a good abstraction, or at least
the name conveys what it does well not to confuse readers.
At first after only seeing
On Thu, Feb 20, 2014 at 3:32 AM, Junio C Hamano gits...@pobox.com wrote:
Nguyễn Thái Ngọc Duy pclo...@gmail.com writes:
(Only nitpicks during this round of review).
+ if (get_device_or_die(path) != get_device_or_die(get_git_dir())) {
+ strbuf_reset(sb);
+
1 - 100 of 3455 matches
Mail list logo
