This question comes up every now and then - how to convert from normal
to bare, or vice versa.
This is just a start to a basic script to go one way. Needs more tests
etc, but it's enough to get newbies (like me) off to a reasonable
start.
PLEASE CC me, as I am not subscribed.
Thanks,
Zenaan
I needed this quite a bit in the last few days, basic script but
serves my need. I think it would be useful for other beginners if in
$git/contrib/ source dir.
Just a start to a basic script. Needs more tests etc, but it's enough
to get newbies (like me) off to a reasonable start. Handles
On 5/27/13, Matthieu Moy matthieu@grenoble-inp.fr wrote:
Zenaan Harkness z...@freedbms.net writes:
rm -rf $repo
The user would appreciate if you check that there are no uncommited
changes and no untracked files (at least no untracked and not ignored
files) before running this.
Also
refspec - git's guilty little secret. Let's milk the guilt.
git branch refspec ought work in a similar way to
git fetch refspec
One syntax to rule them all. Or something.
I just learned how git fetch uses refspecs and how this can just as
well apply to tags to create remote tags
On 6/2/15, Zenaan Harkness z...@freedbms.net wrote:
refspec - git's guilty little secret. Let's milk the guilt.
git branch refspec ought work in a similar way to
git fetch refspec
One syntax to rule them all. Or something.
I just learned how git fetch uses refspecs and how this can just
Please CC me when replying, if you think of it. Thanks.
LWN discussion, this particular thread starts here:
https://lwn.net/Articles/646758/
Some extracts:
Deterministic packfile creation is required for parallel git downloads.
Example git pack file parameter/ configuration variations:
-
Am I missing something in the following:
looking at Documentation/RelNotes/2.10.0.txt I see the following release
note (~line 35):
* "upload-pack" allows a custom "git pack-objects" replacement when
responding to "fetch/clone" via the uploadpack.packObjectsHook.
(merge b738396
Please CC me :)
> From man git-rm:
>
> --cached
> Use this option to unstage and remove paths only from the index.
> Working tree files, whether modified or not, will be left alone.
>
>
> This wording is unclear and dangerous, and ought be cleaned up somehow.
>
> Probably also the
Please CC me :)
>From man git-rm:
--cached
Use this option to unstage and remove paths only from the index.
Working tree files, whether modified or not, will be left alone.
This wording is unclear and dangerous, and ought be cleaned up somehow.
Probably also the option name should
On Sat, Aug 20, 2016 at 08:14:25PM +0100, Philip Oakley wrote:
> From: "Zenaan Harkness" <z...@freedbms.net>
> >
> > Please CC me :)
> > or perhaps something like:
> > "does not unstage a file, it actually stages the removal of the
> > fi
10 matches
Mail list logo
