Am 29.06.2015 um 16:37 schrieb Johannes Schindelin:
> Hi Stefan,
>
> On 2015-06-29 11:07, Stefan Näwe wrote:
>> Am 29.06.2015 um 10:30 schrieb Johannes Schindelin:
>
>>> I just uploaded the 4th release candidate for the upcoming Git for
>>> Windows 2.x release
Am 29.06.2015 um 10:30 schrieb Johannes Schindelin:
> Hi all,
>
> I just uploaded the 4th release candidate for the upcoming Git for
> Windows 2.x release. Please find the download link here:
>
> https://git-for-windows.github.io/#download
>
> The most important changes are the update to Git 2.
Am 17.06.2015 um 18:10 schrieb Robert Dailey:
> I do the following:
>
> $ git push origin :topic
>
> If I stop halfway through typing 'topic' and hit TAB, auto-completion
> does not work if I do not have a local branch by that name (sometimes
> I delete my local branch first, then I push to delet
Am 03.06.2015 um 19:24 schrieb Junio C Hamano:
> Jeff King writes:
>
>> My concern there would be risk of regression. I.e., that we would take
>> some case which used to error out and turn it into a silent noop. So I'd
>> prefer to keep the behavior the same, and just modify the error code
>> pat
Am 01.06.2015 um 11:58 schrieb Jeff King:
> On Mon, Jun 01, 2015 at 11:14:27AM +0200, Stefan Näwe wrote:
>
>> Maybe this one:
>>
>>d3038d (prune: keep objects reachable from recent objects)
>
> Yes, exactly.
>
>> It would be really helpful if you sen
Am 01.06.2015 um 10:52 schrieb Jeff King:
> On Mon, Jun 01, 2015 at 10:40:53AM +0200, Stefan Näwe wrote:
>
>> Turns out to be a tree:
>>
>> tree 7713c3b1e9ea2dd9126244697389e4000bb39d85
>> parent d7acfc22fbc0fba467d82f41c90aab7d61f8d751
>> author Stefan Naewe
Am 01.06.2015 um 10:14 schrieb Jeff King:
> On Mon, Jun 01, 2015 at 09:37:17AM +0200, Stefan Näwe wrote:
>
>> One of my repos started giving an error on 'git gc' recently:
>>
>> $ git gc
>> error: Could not read 7713c3b1e9ea2dd9126244697389e4000
Hi there.
One of my repos started giving an error on 'git gc' recently:
$ git gc
error: Could not read 7713c3b1e9ea2dd9126244697389e4000bb39d85
Counting objects: 3052, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (531/531), done.
Writing objects: 100% (3052/3052)
Am 22.05.2015 um 10:33 schrieb Roberto Tyley:
> [...]
> Hello, I'm stepping up to do that work :) Or at least, I'm implementing a
> one-way GitHub PR -> Mailing list tool, called submitGit:
>
> https://submitgit.herokuapp.com/
That looks really promising!
I wonder if that wouldn't make a good add
Am 27.03.2015 um 13:27 schrieb Garbageyard:
> We use Gitolite for access control and i have admin access on Git server. I
> wanted to make sure that whenever a new repository is created and is then
> cloned on any machine, the default branch should point to mainline. To do
> this, when I run the re
Am 02.03.2015 um 13:02 schrieb Alexander Kuleshov:
> 'was_alias' variable does not need to store it's value on each
> iteration in the loop, anyway this variable changes it's value with run_argv.
s/it's/its/
> 'done_help' variable does not need to be static variable too if we'll move it
> out th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 12.11.2014 um 10:12 schrieb Stefan Näwe:
> Am 12.11.2014 um 09:57 schrieb Thomas Ackermann:
>
>> I also re-read the whole document and think it's still up-to-date
>> with Git 2.0. But I might have missed some subtler points.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 12.11.2014 um 09:57 schrieb Thomas Ackermann:
>
> I also re-read the whole document and think it's still up-to-date
> with Git 2.0. But I might have missed some subtler points.
Hhmm..
At least this is not 100% up to date:
diff --git a/Documentat
Am 07.11.2014 um 20:54 schrieb Junio C Hamano:
> Junio C Hamano writes:
>
>> In other words, you give paths from the command line to tell the
>> command that you want to record the contents of them in the working
>> tree as a whole to be recorded in the resulting commit.
>
> ... and --only/--inc
Hello.
The manpage of git commit reads:
--only
Make a commit only from the paths specified on the command line,
disregarding any contents that have been staged so far. This is
the default mode of operation of git commit if any paths are given
on the command line, in whi
Am 19.08.2014 um 19:15 schrieb Robin Rosenberg:
> Using the original filename suffix for the temporary input files to
> the merge tool confuses IDEs like Eclipse. This patch introduces
> a configurtion option, mergetool.tmpsuffix, which get appended to
> the temporary file name. That way the user c
Am 19.08.2014 um 14:22 schrieb Robin Rosenberg:
> Using the original filename suffix for the temporary input files to
> the merge tool confuses IDEs like Eclipse. This patch introduces
> a configurtion option, mergetool.tmpsuffix, which get appended to
> the temporary file name. That way the user c
Am 18.02.2014 23:54, schrieb Philip Oakley:
> From: "Junio C Hamano"
>> I do not understand why
>> it is even a good idea to show release notes from the command line
>> "git" interface.
>
> My looking at this came from Stefan's suggestion noted above
> $gmane/240595. So it had at least one fol
Am 18.02.2014 00:38, schrieb Johannes Schindelin:
> Dear Git fanbois,
>
> this announcement informs you that the small team of volunteers who keep
> the Git ship afloat for the most prevalent desktop operating system
> managed to release yet another version of Git for Windows:
>
> Git Release Not
Am 29.01.2014 22:21, schrieb Flo:
> I just want to present a small tool I wrote. I use it at work to have
> a tool visualizing the Git basic concepts and data structures which
> "are really really really simple" (Linus' words). That helps me
> teaching my colleagues about Git and answering their qu
Am 22.01.2014 13:53, schrieb Javier Domingo Cansino:
> Will there be any change on how tarballs are distributed, taking into
> account that Google will be shutting down Google Code Downloads
> section[1][2]?
>
Am I missing something or what's wrong with this:
https://github.com/gitster/git/arc
Am 16.01.2014 22:14, schrieb Philip Oakley:
> From: "Stefan Näwe"
> [...]
>>
>> I'd really like to see 'git help relnotes' working as well...
>>
>> Stefan
>
> Stefan,
>
> Were you thinking that all the release notes would be qu
Am 10.01.2014 00:49, schrieb Junio C Hamano:
> I think we already use a nicer way to set up a page alias to keep
> old links working than making a copy in Documentation/; please mimic
> that if possible.
>
> It may be overdue to refresh the suggested set of "top 20" commands,
> as things have vast
Am 27.09.2013 10:07, schrieb Morten Stenshorne:
> I've just upgraded to Debian testing (jessie), and with that I got a
> brand new (for me) git version:
>
> $ git --version
> git version 1.8.4.rc3
>
> Some of my repos I use an ssh tunnel to reach, so when I want to reach a
> repo forwarde
Stefan Näwe atlas-elektronik.com> writes:
> Am 25.09.2013 16:47, schrieb Stefan Näwe:
> This is what it gives me if I use my script (slightly modified
> to also run make) with 'git bisect run':
>
> 6035d6aad8ca11954c0d7821f6f3e7c047039c8f is the first bad commit
An
Am 25.09.2013 16:47, schrieb Stefan Näwe:
> Just a quick report since I don't have time to bisect now (will do later
> if no other gitster is faster...)
I'd marry 'git bisect' if I wasn't already... ;-)
This is what it gives me if I use my script (slightly modif
Am 25.09.2013 16:47, schrieb Stefan Näwe:
> Just a quick report since I don't have time to bisect now (will do later
> if no other gitster is faster...)
Seems to be somewhere between v1.8.3.1 (OK) and v1.8.3.2 (not OK) !!
>
> When I execute the below script 'git s
Just a quick report since I don't have time to bisect now (will do later
if no other gitster is faster...)
When I execute the below script 'git show' crashes. 'git log --oneline -2' gives
for example:
3808bade5b76c4663ac4a3f751dc9f1ed0b08f2e three
error: Could not read 1e8777edeb2b7e757f74c78
Am 01.07.2013 18:46, schrieb Junio C Hamano:
> Stefan Näwe writes:
>
>>> Is there any reason why 'git clone -b' only takes a branch (from
>>> refs/heads/)
>>> or a tag (from refs/tags/) ?
>
> Because they are common enough, and doing the sam
Am 28.06.2013 13:59, schrieb Stefan Näwe:
> Hi there!
>
> Is there any reason why 'git clone -b' only takes a branch (from refs/heads/)
> or a tag (from refs/tags/) ?
>
> Background: At $dayjob we're using some kind of 'hidden' refs (in
> refs/r
Am 28.06.2013 14:18, schrieb Fredrik Gustafsson:
> On Fri, Jun 28, 2013 at 01:59:51PM +0200, Stefan Näwe wrote:
>> Hi there!
>>
>> Is there any reason why 'git clone -b' only takes a branch (from refs/heads/)
>> or a tag (from refs/tags/) ?
>>
>>
Am 28.06.2013 13:59, schrieb Stefan Näwe:
> Hi there!
>
> Is there any reason why 'git clone -b' only takes a branch (from refs/heads/)
> or a tag (from refs/tags/) ?
>
> Background: At $dayjob we're using some kind of 'hidden' refs (in
> refs/r
Hi there!
Is there any reason why 'git clone -b' only takes a branch (from refs/heads/)
or a tag (from refs/tags/) ?
Background: At $dayjob we're using some kind of 'hidden' refs (in
refs/releases/)
to communicate between the 'branch integrator' (who creates the ref in
refs/releases/)
and the '
Am 28.06.2013 11:53, schrieb Chris Packham:
> This allows the user some finer grained control over how the update is
> done. The primary motivation for this was interoperability with stgit
> however being able to intercept the submodule update process may prove
> useful for integrating or extending
Am Donnerstag, 24. Januar 2013 14:40:47 schrieb Duy Nguyen:
> On Thu, Jan 24, 2013 at 7:11 PM, Stefan Näwe
> wrote:
>>> Does it fail with older versions of git? If so, can you bisect?
>>
>> I did. My bisection told me this is the suspect:
>>
>> ccdc603 (
Am 23.01.2013 21:02, schrieb Jeff King:
> On Wed, Jan 23, 2013 at 03:38:16PM +0100, Armin wrote:
>
>> Hello dear git people.
>>
>> I experience a reproducible segmentation fault on one of my
>> repositories when doing a "git log --submodule -p", tested with newest
>> version on Arch Linux (git ver
Am 28.09.2012 10:44, schrieb Stefan Näwe:
> I get "Not a Git repository: remote.git" as well, when I run
> git gui "somewhere" (i.e. not in "remote.git")
i.e.:
$ cd /not/a/repo
$ git gui
> and the select "Open Existing Repository".
>
Am 28.09.2012 10:35, schrieb Frans Klaver:
> Hi,
>
> Please remember to reply to all when discussing things on the git mailing
> list.
>
> On Fri, Sep 28, 2012 at 10:29 AM, Angelo Borsotti
> wrote:
>> Hello
>>
>> I apologise for having used the wrong script to reproduce the error.
>> This is t
Zeeshan Ali (Khattak gnome.org> writes:
>
> Hi,
> Many times I want to refer to 'HEAD^', 'HEAD^^' and sometimes even
> further up the tree. It would be really nice if I didn't have to type
> 'HEAD^' but could only type '^'. Bash completion make things easier
> but it automatically inserts a sp
alum.mit.edu> writes:
>
> From: Michael Haggerty alum.mit.edu>
>
> Add a new Python script, contrib/hooks/post-receive-multimail.py, that
> can be used to send notification emails describing pushes into a git
> repository. This script is derived from
> contrib/hooks/post-receive-mail, but ha
40 matches
Mail list logo
