Christoph Junghans writes:
> Implements a inverted match for "git log", like in the case of
> "git grep -v", which is useful from time to time to e.g. filter
> FIXUP message out of "git log".
>
> Internally, a new bol 'global_invert' has been introduces as
> revs->grep_filter.invert inverts the m
Hello. Thank you for the fix.
Would it be more reliable to compare inode of directory in question
and ".git"? (there is [*] for windows). So that any unspotted name
equivalence is prevented to cause any harm.
*)
http://stackoverflow.com/questions/7162164/does-windows-have-inode-numbers-like-linu
Implements a inverted match for "git log", like in the case of
"git grep -v", which is useful from time to time to e.g. filter
FIXUP message out of "git log".
Internally, a new bol 'global_invert' has been introduces as
revs->grep_filter.invert inverts the match line-wise, which cannot
work as i.e
On Wed, Dec 17, 2014 at 1:32 PM, Stefan Beller wrote:
> From: Ronnie Sahlberg
>
> Add a command line argument to the git push command to request atomic
> pushes.
>
> Signed-off-by: Ronnie Sahlberg
> Signed-off-by: Stefan Beller
> ---
> diff --git a/builtin/push.c b/builtin/push.c
> index a076b1
On Wed, Dec 17, 2014 at 1:32 PM, Stefan Beller wrote:
> From: Ronnie Sahlberg
>
> This adds support to send-pack to negotiate and use atomic pushes
> iff the server supports it. Atomic pushes are activated by a new command
> line flag --atomic.
>
> Signed-off-by: Ronnie Sahlberg
> Signed-off-by:
On Wed, Dec 17, 2014 at 1:32 PM, Stefan Beller wrote:
> From: Ronnie Sahlberg
>
> This adds support to the protocol between send-pack and receive-pack to
> * allow receive-pack to inform the client that it has atomic push capability
> * allow send-pack to request atomic push back.
>
> There is cu
From: Ronnie Sahlberg
Update receive-pack to use an atomic transaction iff the client negotiated
that it wanted atomic-push. This leaves the default behavior to be the old
non-atomic one ref at a time update. This is to cause as little disruption
as possible to existing clients. It is unknown if
On Thu, Dec 18, 2014 at 10:19:19PM +, Dan Langille (dalangil) wrote:
> This is what happens without a valid ticket:
>
> $ git clone https://us.example.com/git/clamav-bytecode-compiler
> Cloning into 'clamav-bytecode-compiler'...
> Username for 'https://us.example.com': dan
> Password for 'http
I am trying to get http://git-scm.com/docs/git-http-backend to auth via
Kerberos.
I have success when a Kerberos ticket is present.
I am trying to get git to authenticate with Kerberos when a ticket is not
present.
Here is what succeeds with a ticket:
SSLOptions +StdenvVars
Options +Exec
On Thu, Dec 18, 2014 at 12:45 PM, Stefan Beller wrote:
> From: Ronnie Sahlberg
>
> Update receive-pack to use an atomic transaction iff the client negotiated
> that it wanted atomic-push. This leaves the default behavior to be the old
> non-atomic one ref at a time update. This is to cause as lit
Hi Stanzilla,
On Thu, 18 Dec 2014, Stanzilla wrote:
> Release notes at
> https://github.com/msysgit/msysgit/raw/master/share/WinGit/ReleaseNotes.rtf
> are *not* up to date.
Yep, the 'master' branch is intentionally behind. It will be updated
tomorrow, as well as the msysgit/git.git repository. T
Dear users of Git for Windows,
a new Git for Windows version has been released, and we urge everybody to
update because it fixes some critical bugs.
Please download the new version from:
https://github.com/msysgit/msysgit/releases/Git-1.9.5-preview20141217
The installer is called Git-1.9.5-prev
Would someone be willing to extend the git-remote-testgit.sh example
[1] with push and fetch capabilities? I am not familiar enough to do
it myself.
Thanks
[1] https://github.com/git/git/blob/master/git-remote-testgit.sh
--
To unsubscribe from this list: send the line "unsubscribe git" in
the bo
The latest maintenance release Git v2.2.1 is now available at
the usual places.
This is a security-fix for CVE-2014-9390, which affects users on
Windows and Mac OS X but not typical UNIX users. A set of new
releases for older maintenance tracks (v1.8.5.6, v1.9.5, v2.0.5, and
v2.1.4) are published
Kenneth Lorber writes:
>> Bug: exit codes from (at least) internal commands are handled incorrectly.
>> E.g. git-merge-file, docs say:
>>The exit value of this program is negative on error, and the number of
>>conflicts otherwise. If the merge was clean, the exit value is 0.
>> Bu
From: Ronnie Sahlberg
Update receive-pack to use an atomic transaction iff the client negotiated
that it wanted atomic-push. This leaves the default behavior to be the old
non-atomic one ref at a time update. This is to cause as little disruption
as possible to existing clients. It is unknown if
On 18.12.14 03:15, Kenneth Lorber wrote:
> The situation is actually slightly more complex than I stated previously.
> From the docs:
> The exit value of this program is negative on error,
> But there’s no such thing as a negative error code under Unix, so (at best)
> that will be exit(255).
>
HELLO
I will like to discuss an oil deal with you,an exportation of 80,000 barrels of
Crude
Oil daily from Iran to Turkey at the rate of $ 70.00 dollars per barrel through
my client company in Iran, this will make you our international representative.
If interested, please reply via my
email.(a
Jonathan Nieder writes:
> Junio C Hamano wrote:
>
>> The issue is if some existing tests will be helped, if we had such a
>> helper.
>
> Since both bin-wrappers/git and test-lib.sh set GIT_TEMPLATE_DIR and
> templates/blt doesn't contain any enabled hooks, I don't see how such
> a helper would be
Stefan Beller writes:
> This would change the current behavior. In the case of !atomic we want
> to consider all commands and not stop early.
Quite right.
> So maybe more
> if (!cmd->error_string) {
> if (!use_atomic
> && ref_transaction_commit(...)) {
> ...
>
Signed-off-by: Alexander Kuleshov
---
pack-bitmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pack-bitmap.c b/pack-bitmap.c
index 6a81841..3281df3 100644
--- a/pack-bitmap.c
+++ b/pack-bitmap.c
@@ -60,7 +60,7 @@ static struct bitmap_index {
struct ewah_bitmap *bl
Ah, yes, didn't know about:
>config variable names are case insensitive
so, you're right, thank you.
--
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 Tue, Dec 16, 2014 at 6:19 PM, Eric Sunshine wrote:
> With the release of Mac OS X 10.7 in July 2011, Apple deprecated all
> openssl.h functionality due to OpenSSL ABI (application binary
> interface) instability, resulting in an explosion of compilation
> warnings about deprecated SSL, SHA1, an
Alexander Kuleshov writes:
> -core.fileMode::
> +core.filemode::
> Tells Git if the executable bit of files in the working tree
> is to be honored.
I do not think that this is a good change: config variable names are
case insensitive, so filemode and fileMode are both correct. The
co
On Wed, 17 Dec 2014 01:09:08 +0630
Arup Rakshit wrote:
[...]
> But I am looking for any differences -
>
> a) git reset --soft and git reset --keep
> b) git reset --hard and git reset --merge
Please consider reading
http://git-scm.com/book/en/v2/Git-Tools-Reset-Demystified
--
To unsubscribe from
Signed-off-by: Alexander Kuleshov
---
Documentation/config.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index f615a5c..a995b68 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -203,7 +203,7 @@ ad
From: 0xAX
Signed-off-by: Alexander Kuleshov
---
Documentation/config.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index f615a5c..a995b68 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -203,7
Junio C Hamano schrieb am 17.12.2014 um 21:53:
> Michael J Gruber writes:
>
>> Rather than extending "git branch" any further[*], I suggest a bolder
>> strategy:
>>
>> - unify/merge for-each-ref and pretty formats (and code) as far as possible
>> - leverage that for the list modes of branch and t
> On Tue, Dec 16, 2014 at 7:39 PM, Arup Rakshit
> wrote:
>> From the command help I see -
>>
>> [arup@to_do_app]$ git reset -h
You can also use "git help reset" to have the full man page.
It has a lot more information.
>> But I am looking for any differences -
Do you have some use cases in min
On Tue, Dec 16, 2014 at 7:39 PM, Arup Rakshit
wrote:
> Hi,
> ..
>
> But I am looking for any differences -
>
> a) git reset --soft and git reset --keep
git reset --keep is a safer version of git reset --hard. It will reset
the working tree. but will abort when it has to overwrite uncomitted
chang
30 matches
Mail list logo
