On Thu, Feb 12, 2015 at 03:31:12PM -0500, Randall S. Becker wrote:
> On the NonStop port, we found that trap was causing an issue with test
> success for t5570. When start_git_daemon completes, the shell (ksh,bash) on
> this platform is sending a signal 0 that is being caught and acted on by the
On Thu, Feb 12, 2015 at 03:32:37PM -0800, Junio C Hamano wrote:
> > and using "Author: " (with no text) does a reset.
>
> no (I do not think it is wrong per-se, but I do not think such a
> good idea).
Fair enough. It is probably a minority use case, and one that is likely
to cause confusion.
>
Currently, a remote helper is only told about the progress and verbosity
options for the 'fetch' and 'push' commands. This means a remote helper
that implements 'import' and 'export' can never know the user requested
progress or verbosity (or lack thereof) through the command line.
Telling the rem
A remote helper is currently only told about the 'check-connectivity',
'cloning', and 'update-shallow' options when it supports the 'fetch'
command, but not when it supports 'import' instead.
This is especially important for the 'cloning' option, because it
means a remote helper that only supports
On 02/12/2015 06:51 PM, Jens Lehmann wrote:
Am 13.02.2015 um 11:57 schrieb Junio C Hamano:
Nguyễn Thái Ngọc Duy writes:
These patches are on top of what's in 'pu'. They add
--ignore-other-worktrees and make a note about current submodule
support status. I don't think submodule support is read
Am 13.02.2015 um 00:38 schrieb Junio C Hamano:
> Karsten Blees writes:
>
>> This is more about copying 'old' things around, which usually also
>> copies mtime on Windows. E.g.:
>>
>> # create two files with slightly different mtime
>> for i in {1..10}; do (echo "v1" >> test); done &&
>> for
On Thu, Feb 12, 2015 at 4:17 PM, David Glasser wrote:
> On Thu, Feb 12, 2015 at 2:34 PM, Junio C Hamano wrote:
>> David Glasser writes:
>>
>>> So to be concrete: What I'm proposing (and I'm excited to implement
>>> it!) is the following:
>>>
>>> When running "git commit" and:
>>> - You've fallen
On Thu, Feb 12, 2015 at 2:34 PM, Junio C Hamano wrote:
> David Glasser writes:
>
>> So to be concrete: What I'm proposing (and I'm excited to implement
>> it!) is the following:
>>
>> When running "git commit" and:
>> - You've fallen into the case where the message was read from SQUASH_MSG
>> - Y
Am 13.02.2015 um 11:57 schrieb Junio C Hamano:
Nguyễn Thái Ngọc Duy writes:
These patches are on top of what's in 'pu'. They add
--ignore-other-worktrees and make a note about current submodule
support status. I don't think submodule support is ready yet even
with Max Kirillov's series [1]. H
Am 13.02.2015 um 00:15 schrieb Thomas Braun:
> Am 12.02.2015 um 00:53 schrieb Karsten Blees:
>> diff --git a/config.mak.uname b/config.mak.uname
>> index b64b63c..a18a4cc 100644
>> --- a/config.mak.uname
>> +++ b/config.mak.uname
>> @@ -346,7 +346,7 @@ ifeq ($(uname_S),Windows)
>> NO_SVN_TESTS
Karsten Blees writes:
> This is more about copying 'old' things around, which usually also
> copies mtime on Windows. E.g.:
>
> # create two files with slightly different mtime
> for i in {1..10}; do (echo "v1" >> test); done &&
> for i in {1..10}; do (echo "v2" >> test2); done
> # wait a
Jeff King writes:
> What happens if there is no "Author:" line in the output?
I've been assuming that we would do what the current code does.
"git commit --amend" for example internally remembers who the
original author was and uses that, without paying any attention to
the result from the edito
These two patches
* bp/diff-relative-config (2015-01-07) 2 commits
- diff: teach diff.relative to give default to --relative=
- diff: teach --no-relative to override earlier --relative
have been sitting in my Undecided pile, primarily because I am wary
of touching a core command lik
Am 12.02.2015 um 00:53 schrieb Karsten Blees:
> We no longer use any of MSVCRT's stat-functions, so there's no need to
> stick to a CRT-compatible 'struct stat' either.
>
> Define and use our own POSIX-2013-compatible 'struct stat' with nanosecond-
> precision file times.
>
> Signed-off-by: Karst
"Kyle J. McKay" writes:
> Since it's really not very difficult or invasive to add support for
> the no- variants, here's a patch to do so:
I am inclined to replace the tc/t9001-noxmailer topic that has been
sitting on my Undecided pile with this patch and move it forward.
* tc/t9001-noxma
Junio C Hamano writes:
> Jeff King writes:
>
>> On Fri, Dec 05, 2014 at 10:00:05AM -0800, Junio C Hamano wrote:
>>
>>> I am more worried about variable length part pushing the information
>>> that is given later out to the right, e.g. "error: missing file '%s'
>>> prevents us from doing X". Cho
On Thu, Feb 12, 2015 at 03:01:18PM -0800, Junio C Hamano wrote:
> Jeff King writes:
>
> > This is a re-roll of this series:
> >
> > http://thread.gmane.org/gmane.comp.version-control.git/260922/focus=261374
> >
> > from early December to move the strbuf documentation into the header
> > file.
Jeff King writes:
> This is a re-roll of this series:
>
> http://thread.gmane.org/gmane.comp.version-control.git/260922/focus=261374
>
> from early December to move the strbuf documentation into the header
> file.
>
> And of course the elephant in the room is the other dozen or more
> api-*.txt
Nguyễn Thái Ngọc Duy writes:
> These patches are on top of what's in 'pu'. They add
> --ignore-other-worktrees and make a note about current submodule
> support status. I don't think submodule support is ready yet even
> with Max Kirillov's series [1]. His 03/03 is already fixed in 'pu'
> though
Am 12.02.2015 um 20:48 schrieb Junio C Hamano:
> Karsten Blees writes:
>
>> However, some users have expressed concerns that 'same size and
>> mtime' [2] may theoretically happen by chance in daily operation.
>
> Hmph.
>
> Haven't we already accepted that it is not just "may theoretically
> hap
Junio C Hamano writes:
> Scott Schmit writes:
>>
>> Considering the man page says create & store are intended for scripts
>> and "probably not the command you want to use", why would we want it in
>> the synopsis?
>
> With the understanding that these are only for scripters, I think we
> can agr
On Thu, Feb 12, 2015 at 02:34:43PM -0800, Junio C Hamano wrote:
> I actually was hoping that this would extend to cases other than
> "git merge --squash".
>
> When running "git commit" and:
>
> - You didn't use a more explicit method of specifying the
>authorship identity (--author, --date,
So after discussing this one and queuing the resulting three-patch
series jk/sanity that consists of the three patches:
* jk/sanity (2015-01-27) 3 commits
- test-lib.sh: set prerequisite SANITY by testing what we really need
- tests: correct misuses of POSIXPERM
- t/lib-httpd: s
David Glasser writes:
> So to be concrete: What I'm proposing (and I'm excited to implement
> it!) is the following:
>
> When running "git commit" and:
> - You've fallen into the case where the message was read from SQUASH_MSG
> - You haven't used another method of specifying the author (--author
Hi,
On 2015-02-12 20:48, Junio C Hamano wrote:
> Karsten Blees writes:
>
>> This patch series was inspired by the problem that Git does not
>> detect changed file content if st_size, st_mtime and st_ctime
>> are unchanged. This was apparently caused by VSS2Git resetting
>> mtime to a value in th
On Thu, Feb 12, 2015 at 2:16 PM, David Glasser wrote:
> - Before invoking prepare-commit-msg, all of the `Author:` lines found
> in SQUASH_MSG have the same value
OK, and to be very specific: I'm just proposing "literally the same
text written after Author"; using mailmap to detect that multipl
On Thu, Feb 12, 2015 at 1:23 PM, Junio C Hamano wrote:
> David Glasser writes:
>
>> Well, using -c appears to override SQUASH_MSG entirely; it replaces
>> the message as well as the author. Often I do want to make my own
>> message based on all the messages provided by the submitter. (And
>> ty
On Mon, Feb 09, 2015 at 10:12:42AM +0100, Michael Haggerty wrote:
> if (!(flags & EXPIRE_REFLOGS_DRY_RUN)) {
> + /*
> + * It doesn't make sense to adjust a reference pointed
> + * to by a symbolic ref based on expiring entries in
> + * the s
David Glasser writes:
> Well, using -c appears to override SQUASH_MSG entirely; it replaces
> the message as well as the author. Often I do want to make my own
> message based on all the messages provided by the submitter. (And
> typically the branch's tip is the least useful message anyway: it
Alessandro Di Marco writes:
> Junio C Hamano writes:
>
>> More importantly, adding non-essential stuff left and right will force
>> third party Git reimplementations to pay attention to them and also
>> will leave room for them to make mistakes when deciding what to
>> propagate, what to drop an
On Thu, Feb 12, 2015 at 12:18 PM, Junio C Hamano wrote:
> Jeff King writes:
>
>> On Wed, Feb 11, 2015 at 09:21:04AM -0800, David Glasser wrote:
>>
>>> (I'm not sure if this should be a flag to --squash or to commit.
>>> Maybe `git merge --squash`; `git commit --use-squashed-author`? Seems
>>> li
Junio C Hamano writes:
> Ævar Arnfjörð Bjarmason writes:
>> We've already told clients for a long time to ignore fields they
>> don't know about,
> Yes, but the reason that mechanism is there is not because we want to
> add random cruft Git does not have to know about. It is to avoid
> older
Good eyes.
This one is a straight-forward bugfix for 0ea47f9d (signed push:
teach smart-HTTP to pass "git push --signed" around, 2014-09-15);
will queue directly to jc/push-cert branch and will merge to
maintenance tracks independent from the other two.
Thanks.
--
To unsubscribe from this list: s
On the NonStop port, we found that trap was causing an issue with test
success for t5570. When start_git_daemon completes, the shell (ksh,bash) on
this platform is sending a signal 0 that is being caught and acted on by the
trap command within the start_git_daemon and stop_git_daemon functions. I
Mike Hommey writes:
> Currently, the progress and verbosity options are only emitted for the fetch
> and push commands, but they should also be emitted for other commands, such as
> import or export, and, why not, even list.
>
> Signed-off-by: Mike Hommey
> ---
I had a hard time understanding w
On 24.01.2015 00:37, Jeff King wrote:
GitHub is organizing a Git-related conference to be held April 8-9,
2015, in Paris. Details here:
http://git-merge.com/
The exact schedule is still being worked out, but there is going to be
some dedicated time/space for Git (and libgit2 and JGit) deve
On 24.01.2015 00:37, Jeff King wrote:
GitHub is organizing a Git-related conference to be held April 8-9,
2015, in Paris. Details here:
http://git-merge.com/
The exact schedule is still being worked out, but there is going to be
some dedicated time/space for Git (and libgit2 and JGit) deve
Jeff King writes:
> On Wed, Feb 11, 2015 at 09:21:04AM -0800, David Glasser wrote:
>
>> (I'm not sure if this should be a flag to --squash or to commit.
>> Maybe `git merge --squash`; `git commit --use-squashed-author`? Seems
>> like it should be not too hard to implement; SQUASH_MSG is pretty
>
On 24.01.2015 00:37, Jeff King wrote:
GitHub is organizing a Git-related conference to be held April 8-9,
2015, in Paris. Details here:
http://git-merge.com/
The exact schedule is still being worked out, but there is going to be
some dedicated time/space for Git (and libgit2 and JGit) deve
Michael Haggerty writes:
> This is a pretty exotic usage. I can't think of any real-life use case
> for using "--updateref" together with a symbolic reference. In our
> entire code base, "--updateref" is only used a single time, in
> "git-stash.sh", and that is always for "refs/stash", which is n
Michael Haggerty writes:
> On 02/11/2015 12:42 AM, Stefan Beller wrote:
>> On Mon, Feb 9, 2015 at 1:12 AM, Michael Haggerty
>> wrote:
>>> ---all::
>>> - Instead of listing explicitly, prune all refs.
>>> +--stale-fix::
>>> + This revamps the logic -- the definition of "broken commi
Michael Haggerty writes:
> write_ref_sha1() previously skipped the write if the reference already
> had the desired value, unless lock->force_write was set. Instead,
> perform that test at the callers.
>
> Two of the callers (in rename_ref()) unconditionally set force_write
> just before calling
Jeff King writes:
> The beginnings of the Google Summer of Code deadlines are upon us again.
> Organization applications are due February 20th (next Friday).
>
> - Any thoughts on procedures or lessons learned from last year?
>
>Personally, I really liked the "micro-project" system from last
Karsten Blees writes:
> This patch series was inspired by the problem that Git does not
> detect changed file content if st_size, st_mtime and st_ctime
> are unchanged. This was apparently caused by VSS2Git resetting
> mtime to a value in the past. [1]
>
> I believe (or rather hope) that all invo
Modulo minor nits, this round looks nicely done.
--
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
Good.
--
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
Michael Haggerty writes:
> diff --git a/t/t7516-commit-races.sh b/t/t7516-commit-races.sh
> new file mode 100755
> index 000..08e6a6c
> --- /dev/null
> +++ b/t/t7516-commit-races.sh
> @@ -0,0 +1,33 @@
> +#!/bin/sh
> +
> +test_description='git commit races'
> +. ./test-lib.sh
> +
> +test_tick
Valery Yundin wrote:
> On 31 January 2015 at 13:51, Nico Schlömer wrote:
> > I tried the patch and I still get
> > ```
> > [...]
> > r100 = e2a9b5baa2cebb18591ecb04ff350410d52f36de (refs/remotes/git-svn)
> > Unexpected result returned from git cat-file at
> > /home/nschloe/share/perl/5.18.2/Git/S
Stefan Beller writes:
> On Thu, Feb 12, 2015 at 3:12 AM, Michael Haggerty
> wrote:
>> - int flags; /* REF_NODEREF? */
>> - int have_old; /* 1 if old_sha1 is valid, 0 otherwise */
>> + /*
>> +* One or more of REF_HAVE_OLD, REF_NODEREF,
>> +* REF_DELETING, and RE
On Thu, Feb 12, 2015 at 4:12 AM, Jeff King wrote:
> On Thu, Feb 12, 2015 at 12:35:48PM +0100, Michael Haggerty wrote:
>
>> > I assume you are already munging in your editor the template provided by
>> > "git commit" after the squash? What would be really nice, IMHO, is if
>> > there was a way to s
On Thu, Feb 12, 2015 at 3:12 AM, Michael Haggerty wrote:
Reviewed-by: Stefan Beller
--
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
On Thu, Feb 12, 2015 at 3:12 AM, Michael Haggerty wrote:
> Committing involves the following steps:
>
> 1. Determine the current value of HEAD (if any).
> 2. Create the new commit object.
> 3. Update HEAD.
>
> Please note that step 2 can take arbitrarily long, because it might
> involve the user e
On Thu, Feb 12, 2015 at 3:12 AM, Michael Haggerty wrote:
> - int flags; /* REF_NODEREF? */
> - int have_old; /* 1 if old_sha1 is valid, 0 otherwise */
> + /*
> +* One or more of REF_HAVE_OLD, REF_NODEREF,
> +* REF_DELETING, and REF_IS_PRUNING:
> +*/
> +
On Thu, Feb 12, 2015 at 8:52 AM, Michael Haggerty wrote:
> On 02/12/2015 12:25 AM, Stefan Beller wrote:
>> On Wed, Feb 11, 2015 at 2:49 PM, Junio C Hamano wrote:
>>> Stefan Beller writes:
>>>
On Mon, Feb 9, 2015 at 1:12 AM, Michael Haggerty
wrote:
> When processing the reflog of
On Thu, Feb 12, 2015 at 3:12 AM, Michael Haggerty wrote:
> Instead, verify the reference's old value if and only if old_sha1 is
> non-NULL.
>
>...
> @@ -3664,9 +3664,6 @@ int ref_transaction_update(struct ref_transaction
> *transaction,
> if (transaction->state != REF_TRANSACTION_OPEN)
>
On Thu, Feb 12, 2015 at 8:08 AM, Michael Haggerty wrote:
> On 02/11/2015 01:44 AM, Stefan Beller wrote:
>> On Mon, Feb 9, 2015 at 1:12 AM, Michael Haggerty
>> wrote:
>>
>>> If we are expiring reflog entries for a symbolic reference, then how
>>> should --updateref be handled if the newest reflog
On 02/12/2015 12:25 AM, Stefan Beller wrote:
> On Wed, Feb 11, 2015 at 2:49 PM, Junio C Hamano wrote:
>> Stefan Beller writes:
>>
>>> On Mon, Feb 9, 2015 at 1:12 AM, Michael Haggerty
>>> wrote:
When processing the reflog of a symbolic ref, hold the lock on the
symbolic reference itsel
On 02/11/2015 01:44 AM, Stefan Beller wrote:
> On Mon, Feb 9, 2015 at 1:12 AM, Michael Haggerty wrote:
>
>> If we are expiring reflog entries for a symbolic reference, then how
>> should --updateref be handled if the newest reflog entry is expired?
>>
>> Option 1: Update the referred-to reference
On 02/11/2015 12:12 AM, Stefan Beller wrote:
> Signed-off-by: Stefan Beller
> ---
>
> Notes:
> When this patch series is applied, you only have 3 occurences of
> force_write.
>
> 1. In the struct as an undocumented int.
> 2. In lock_ref_sha1_basic:
> if ((flags & REF_NODE
On 02/11/2015 12:42 AM, Stefan Beller wrote:
> On Mon, Feb 9, 2015 at 1:12 AM, Michael Haggerty wrote:
>> ---all::
>> - Instead of listing explicitly, prune all refs.
>> +--stale-fix::
>> + This revamps the logic -- the definition of "broken commit"
>> + becomes: a commit that i
Sorry, I don't know what this TOP posting problem is, and hitting
reply only replies to the last sender. If you prefer, and you have
some regular bugtracker, I could use that instead of email posting.
To repro-
Set up git user on local linux repo, in my case 192.168.0.100
On a windows 7 64bit m
Am Donnerstag, den 12.02.2015, 07:21 -0500 schrieb Erik Friesen:
> I'd say this is related. http://sourceforge.net/p/mingw/bugs/2240/
>
> There isn't much hope, that was filed months ago with no action. I
> suggest moving to another ssh library perhaps? Anyways, this is a
> windows git bug repo
> -Original Message-
> From: Erik Friesen
> Sent: Thursday, February 12, 2015 7:22
>
> I'd say this is related. http://sourceforge.net/p/mingw/bugs/2240/
>
> There isn't much hope, that was filed months ago with no action. I
> suggest moving to another ssh library perhaps? Anyways, thi
Hi there,
I have been running:
repo = Rugged::Config.global
type = "commit"
tagname = "v99.99.2"
username = repo["user.name"]
email = repo["user.email"]
message = "this is the message for the annotated tag"
tag_contents =
"object f849f9e28c7f36a826d4b451efb16516c0c3acc2\ntype #{type}\ntag #
{tagn
Also, as another nuance of this bug, this destroyed the local repo in
the process, inserting >> HEAD, , << wrote:
> I'd say this is related. http://sourceforge.net/p/mingw/bugs/2240/
>
> There isn't much hope, that was filed months ago with no action. I
> suggest moving to another
I'd say this is related. http://sourceforge.net/p/mingw/bugs/2240/
There isn't much hope, that was filed months ago with no action. I
suggest moving to another ssh library perhaps? Anyways, this is a
windows git bug report, so it really needs to stay with mysgit in my
opinion.
I'd say it shoul
On Thu, Feb 12, 2015 at 12:35:48PM +0100, Michael Haggerty wrote:
> > I assume you are already munging in your editor the template provided by
> > "git commit" after the squash? What would be really nice, IMHO, is if
> > there was a way to set the author during that edit (e.g., by moving one
> > o
On 02/11/2015 01:05 AM, Jeff King wrote:
> On Tue, Feb 10, 2015 at 03:24:47PM -0800, Stefan Beller wrote:
>
>> On Mon, Feb 9, 2015 at 1:12 AM, Michael Haggerty
>> wrote:
>>> If a reference is missing, its SHA-1 will be null_sha1, which can't
>>> possibly match a new value that ref_transaction_co
On 02/09/2015 09:55 PM, Eric Sunshine wrote:
> On Mon, Feb 9, 2015 at 4:12 AM, Michael Haggerty wrote:
>> [...]
>> But we don't want the repository in an invalid state even temporarily,
>> and we don't want leave an invalid state if other callers of "git
>
> s/want/want to/
> [...]
Thanks; will
On 02/12/2015 10:28 AM, Jeff King wrote:
> On Wed, Feb 11, 2015 at 09:21:04AM -0800, David Glasser wrote:
>
>> (I'm not sure if this should be a flag to --squash or to commit.
>> Maybe `git merge --squash`; `git commit --use-squashed-author`? Seems
>> like it should be not too hard to implement;
Add a docstring for update_ref(), emphasizing its similarity to
ref_transaction_update(). Rename its parameters to match those of
ref_transaction_update().
Signed-off-by: Michael Haggerty
Reviewed-by: Stefan Beller
---
refs.c | 8
refs.h | 15 +++
2 files changed, 15 inser
It makes no sense to delete a reference that is already known not to
exist.
Signed-off-by: Michael Haggerty
Reviewed-by: Stefan Beller
---
refs.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/refs.c b/refs.c
index 3f78fac..9dd7932 100644
--- a/refs.c
+++ b/refs.c
@@ -3702,6 +3702,8 @@ i
Creating a reference requires a new_sha1 that is not NULL and not
null_sha1.
Signed-off-by: Michael Haggerty
Reviewed-by: Stefan Beller
---
refs.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/refs.c b/refs.c
index ddb8bca..3f78fac 100644
--- a/refs.c
+++ b/refs.c
@@ -3690,6 +3690,8 @@
If HEAD doesn't point at anything during the initial check, then we
should make sure that it *still* doesn't point at anything when we are
ready to update the reference. Otherwise, another process might commit
while we are working (e.g., while we are waiting for the user to edit
the commit message)
Instead, verify the reference's old value if and only if old_sha1 is
non-NULL.
Signed-off-by: Michael Haggerty
Reviewed-by: Stefan Beller
---
builtin/receive-pack.c | 3 +--
builtin/update-ref.c | 5 +++--
refs.c | 11 ++-
refs.h | 6 +++---
4 files
Instead of having a separate have_old field, record this boolean value
as a bit in the "flags" field.
Signed-off-by: Michael Haggerty
---
refs.c | 45 -
1 file changed, 28 insertions(+), 17 deletions(-)
diff --git a/refs.c b/refs.c
index 4de1383..6cfc
This is v2 of the patch series, with only minor changes from v1 [1].
Thanks to Stefan Beller and Junio for their feedback about v1. I think
I have addressed all of the points that were raised.
Changes since v1:
* Rebased onto new upstream master (because it now includes the
dependencies, mh/ref
Committing involves the following steps:
1. Determine the current value of HEAD (if any).
2. Create the new commit object.
3. Update HEAD.
Please note that step 2 can take arbitrarily long, because it might
involve the user editing a commit message.
If a second process sneaks in a commit during
There is no reason to "reserve" a gap between the public and private
flags values.
Signed-off-by: Michael Haggerty
---
refs.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/refs.c b/refs.c
index 5e6355c..4de1383 100644
--- a/refs.c
+++ b/refs.c
@@ -44,7 +44,8 @@ static uns
If NULL is passed to ref_transaction_update()'s new_sha1 parameter,
then just verify old_sha1 (under lock) without trying to change the
new value of the reference.
Use this functionality to add a new function ref_transaction_verify(),
which checks the current value of the reference under lock but
It is only used internally now. Document it a little bit better, too.
Signed-off-by: Michael Haggerty
Reviewed-by: Stefan Beller
---
refs.c | 6 ++
refs.h | 4 +---
2 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/refs.c b/refs.c
index ab2f2a9..5e6355c 100644
--- a/refs.c
+++
Add more information to the comment introducing the four reference
transaction update functions, so that each function's docstring
doesn't have to repeat it. Add a pointer from the individual
functions' docstrings to the introductory comment.
Signed-off-by: Michael Haggerty
---
refs.h | 66 +
Instead, verify the reference's old value if and only if old_sha1 is
non-NULL.
ref_transaction_delete() will get the same treatment in a moment.
Signed-off-by: Michael Haggerty
Reviewed-by: Stefan Beller
---
branch.c | 5 +++--
builtin/commit.c | 2 +-
builtin/fetch.c
On Thu, Feb 12, 2015 at 07:10:01PM +0900, Mike Hommey wrote:
> Signed-off-by: Mike Hommey
> ---
> transport-helper.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/transport-helper.c b/transport-helper.c
> index c3868e4..b72fd4a 100644
> --- a/transport-helper.c
> +++ b
Currently, the progress and verbosity options are only emitted for the fetch
and push commands, but they should also be emitted for other commands, such as
import or export, and, why not, even list.
Signed-off-by: Mike Hommey
---
transport-helper.c | 5 +++--
1 file changed, 3 insertions(+), 2 d
The check-connectivity, cloning, and update-shallow options are currently only
emitted for the fetch command but should also be emitted for the import
command.
Signed-off-by: Mike Hommey
---
transport-helper.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --g
Signed-off-by: Mike Hommey
---
transport-helper.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/transport-helper.c b/transport-helper.c
index c3868e4..b72fd4a 100644
--- a/transport-helper.c
+++ b/transport-helper.c
@@ -861,7 +861,7 @@ static int push_refs_with_export(struct
The beginnings of the Google Summer of Code deadlines are upon us again.
Organization applications are due February 20th (next Friday).
- Do we want to do it?
- Who would like to volunteer to be the org admin?
I would like for it not to be me again, but I can help walk anyone
through the
On Thu, Feb 12, 2015 at 1:33 AM, Erik Friesen wrote:
> Pushing over http and https are unaffected.. My linux nas died, so on
> rebuild I tried to do the ssh thing, and realized quite soon that
> things weren't right.
>
> As far as other uses of ssh, I don't know, I use putty frequently, but
> I a
On Wed, Feb 11, 2015 at 09:21:04AM -0800, David Glasser wrote:
> (I'm not sure if this should be a flag to --squash or to commit.
> Maybe `git merge --squash`; `git commit --use-squashed-author`? Seems
> like it should be not too hard to implement; SQUASH_MSG is pretty
> parseable. Or just a con
Kevin yahoo.com> writes:
> that the CTRL+Arrow keys are not sending any unique sequences. These
> sequences are distinct and can be bound as I am describing when using the
> "mintty.exe" xterm terminal emulator. So why are they not working when I
Note that mintty does not work properly with (i
91 matches
Mail list logo
