Hi All
I am fairly new to git, however I have a challenge of upgrading git from 2.0.4
to 2.4.12 and my initial 2.0.4 install was done via TAR BALL on my server.
I have a centos server running git and Atlassian STASH and my challenge is for
me to upgrade the STASH application I need to move to a
6th iteration of the reftable storage format.
You can read a rendered version of this here:
https://googlers.googlesource.com/sop/jgit/+/reftable/Documentation/technical/reftable.md
Changes from v5:
- extensions.refStorage = reftable is used to select this format.
- Log records can be explicitly
Jeff King writes:
> That is fine by me. AFAIK, we already build the curl support by default
> when a sufficiently-advanced version of curl is available. So if there
> were feature-parity problems hopefully somebody would have reported it.
>
> I think the deprecation here can be relatively fast be
Ævar Arnfjörð Bjarmason writes:
> Change an argument to test_line_count (which'll ultimately be turned
> into a "test" expression) to use "-gt" instead of ">" for an
> arithmetic test.
>
> This broken on e.g. OpenBSD as of v2.13.0 with my commit
> ac3f5a3468 ("ref-filter: add --no-contains optio
Michael Forney writes:
> Ah. Well, it looks like all but git-merge-resolve.sh run `.
> git-sh-setup`, so we know that GIT_EXEC_PATH must in their PATH (and
> at the front unless the script was invoked directly).
>
> git-merge-resolve.sh does not do this, so I suppose if the user ran
> $GIT_EXEC_P
On Sun, Aug 06, 2017 at 11:38:50PM +, Ævar Arnfjörð Bjarmason wrote:
> Change an argument to test_line_count (which'll ultimately be turned
> into a "test" expression) to use "-gt" instead of ">" for an
> arithmetic test.
>
> This broken on e.g. OpenBSD as of v2.13.0 with my commit
> ac3f5a346
Change an argument to test_line_count (which'll ultimately be turned
into a "test" expression) to use "-gt" instead of ">" for an
arithmetic test.
This broken on e.g. OpenBSD as of v2.13.0 with my commit
ac3f5a3468 ("ref-filter: add --no-contains option to
tag/branch/for-each-ref", 2017-03-24).
U
On Sun, Aug 6, 2017 at 9:56 AM, Ævar Arnfjörð Bjarmason
wrote:
> On Sun, Aug 06 2017, Shawn Pearce jotted:
>
>> 5th iteration of the reftable storage format.
>
> I haven't kept up with all of the discussion, sorry if these comments
> repeat something that's already mentioned.
>
>> ### Version 1
>>
Liebste,
Wie gehts Ihnen heute, ich hoffe, dass meine Post Sie in gutem Zustand
der Gesundheit erfüllt? Sehr geehrte Damen und Herren, ich habe mich
entschlossen, mit Ihnen in Kontakt zu treten, wenn ich bedenkt habe,
dass wir uns noch nicht getroffen haben, aber wegen eines Umstandes,
der mi
GOOD DAY,WE ARE OFFERING FINANCING ASSISTANCE AT 2% INTEREST RATE IF YOU NEED A
LOAN CONTACT US
Le 04/08/2017 à 23:22, Jeff King a écrit :
> On Fri, Aug 04, 2017 at 02:18:13PM -0700, Junio C Hamano wrote:
>
>>> I also think it might be reasonable to scrap all of this ad-hoc imap
>>> code in favor of curl, which already gets these cases right. We already
>>> have a curl-backed implementation.
On Sat, Aug 05 2017, Junio C. Hamano jotted:
> Ævar Arnfjörð Bjarmason writes:
>
>> We've talked how this UX should look before on-list. Rather than
>> re-hashing the arguments I had before I thought it was useful to present
>> it as a table. Here's how the patch looks now:
>>
>>
>> |--
> On 26 Jul 2017, at 20:17, Jonathan Tan wrote:
>
> Refactor, into a common function, the version and capability negotiation
> done when invoking a long-running process as a clean or smudge filter.
> This will be useful for other Git code that needs to interact similarly
> with a long-running pr
```
git checkout -b new_branch
```
Git does what's asked except that Git's success response ("Switched to a new
branch 'new_branch'"), goes to to stderr instead of stdout.
This feels against standard unix conventions of what to output to stderr v
stdout. It's an extra jump that people scripti
Hi all :)
I just wanted to let you know how are we going :)
We can say now that we are international! New members are working with
us from Venezuela!
By now we are on the 50% of our git translation project, we hope to
have it ready for the next release :)
This is our first draft of the websit
On Sun, Aug 06 2017, Shawn Pearce jotted:
> 5th iteration of the reftable storage format.
I haven't kept up with all of the discussion, sorry if these comments
repeat something that's already mentioned.
> ### Version 1
>
> A repository must set its `$GIT_DIR/config` to configure reftable:
>
>
> On 06 Aug 2017, at 01:00, Johannes Schindelin
> wrote:
>
> Dear Git users,
>
> It is my pleasure to announce that Git for Windows 2.14.0 is available from:
Thank you :-)
> * It is now possible to switch between Secure Channel and OpenSSL for
>Git's HTTPS transport by setting the http
Am 06.08.2017 um 01:00 schrieb Johannes Schindelin:
Dear Git users,
It is my pleasure to announce that Git for Windows 2.14.0 is available from:
https://git-for-windows.github.io/
Changes since Git for Windows v2.13.3 (July 13th 2017)
Thank you so much! One question, though:
New Fe
18 matches
Mail list logo
