inks, etc.
to not to make anyone web search anything for you.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
nd warnings from git may be quite annoying. Given the fact there is not
one but may valid "my way"-s available, acceptable and supported by Git,
I think, babysitting behaviour is not quite aligned with its philosophy, is it?
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
On 19-08-01 13:24:00, Junio C Hamano wrote:
Mateusz Loskot writes:
Is there any other way, without remembering to `git merge` with `--log`?
"git config merge.log true"?
That's sweet! Thank you
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
Fingerprint=C081 EA1B
messages of intermediate commits into merge commit message
using `git merge --log feature1`.
Is there any other way, without remembering to `git merge` with `--log`?
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
On Fri, 5 Jul 2019 at 18:25, Torsten Bögershausen wrote:
> On Fri, Jul 05, 2019 at 01:35:13PM +0200, Mateusz Loskot wrote:
> >
> > Using git version 2.22.0.windows.1
> >
> > I have a repository with number of .txt files encoded in
> > little-endian UTF-16 wi
e UTF-16LE-BOM files.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
On Mon, 1 Jul 2019 at 14:33, Johannes Schindelin
wrote:
> On Sat, 29 Jun 2019, Mateusz Loskot wrote:
>
> > I have a script which I have used for long time, with numerous
> > git commands and one of commands is this trivial:
> >
> > git submodule foreach --recu
;t find any related changes in the release notes.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
ee features of Git,
and choose the one that suits best your workflow(s) to implement your
repositories structure.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
see the problem.
It seems like a bug in earlier version indeed, that has been fixed now.
Brian, yes, the .gitmodules was perfectly correct.
Brian, Duy, Jeff, thank you all for responding; the problem has
been solved for me now.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
Hmm, sorry for pushing, but no ideas, really?
Doesn't it seem like a bug?
Matz
On Tue, 19 Feb 2019 at 17:51, Mateusz Loskot wrote:
>
> Hi,
>
> $ git version
> git version 2.20.1.windows.1
>
> I'm running `git clone --recurse-submodules https://...`
> The comma
Hi,
$ git version
git version 2.20.1.windows.1
I'm running `git clone --recurse-submodules https://XXX`
The command seems to run well and completes with success.
However, I noticed strange output from git:
```
Submodule 'Binary/A' (https://XXX) registered for path '!f() {
~/AppData/Local/Fork/F
his is very similar to what we plan to do:
> https://www.stickermule.com/unixstickers.
I'd follow the following steps:
Go to https://git-scm.com/downloads/logos
Scroll to the bottom
Follow link to Creative Commons Attribution 3.0 Unported License
Read and understand it, or hire a lawyer.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
n general is still experimental, and the support
for submodules is incomplete.
It is NOT recommended to make multiple checkouts of a superproject."
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
, at which point?
git gc --aggressive --prune=now
git submodule foreach --recursive git gc --aggressive --prune=now
Please, assume, no new commits will happen locally between the
`git clone --branch master ...` and `cp -a repo_master ...`.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
is x10-x100... faster than `git svn`.
[1] https://subgit.com/
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
On Thu, 29 Nov 2018 at 16:39, Ævar Arnfjörð Bjarmason wrote:
> On Thu, Nov 29 2018, Mateusz Loskot wrote:
> > On Thu, 29 Nov 2018 at 16:03, Ævar Arnfjörð Bjarmason
> > wrote:
> >> On Wed, Nov 28 2018, Mateusz Loskot wrote:
> >> >
> >> > (using
On Thu, 29 Nov 2018 at 16:03, Ævar Arnfjörð Bjarmason wrote:
> On Wed, Nov 28 2018, Mateusz Loskot wrote:
> >
> > (using git version 2.19.2.windows.1)
> >
> > I've just encountered one of those WTH moments.
> >
> > I have a bare repository
> >
On Thu, 29 Nov 2018 at 14:40, Randall S. Becker wrote:
> On November 29, 2018 6:56, Mateusz Loskot wrote:
> > On Thu, 29 Nov 2018 at 12:50, Stefanie Leisestreichler
> > wrote:
> > >
> > > git tag -a 0.9.0
> > > git push origin master
> > >
&g
citly push tags to a shared server after you
have created them."
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
On Wed, 28 Nov 2018 at 17:50, Mateusz Loskot wrote:
>
> (using git version 2.19.2.windows.1)
> [...]
> I restored the repo and tried out
>
> git push origin 1.0
> git push origin --tags
>
> and this time both succeeded, without wiping out any refs.
And, to my surpris
ld anyone help me to understand why remote-less
git push --tags
is/was so dangerous and unforgiving?!
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
d-workflows
[2] https://www.atlassian.com/git/articles/git-team-workflows-merge-or-rebase
[3]
https://reallifeprogramming.com/git-process-that-works-say-no-to-gitflow-50bf2038ccf7
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
On Mon, 12 Nov 2018 at 00:47, Mateusz Loskot wrote:
>
> Hi,
>
> I'm posting here for the first time and I hope it's the right place to ask
> questions about Git LFS.
>
> TL;TR: Is this normal a repository migrated to Git LFS inflates multiple times
> and how to
On Mon, 12 Nov 2018 at 13:31, Jeff King wrote:
> On Mon, Nov 12, 2018 at 12:47:42AM +0100, Mateusz Loskot wrote:
> >
> > TL;TR: Is this normal a repository migrated to Git LFS inflates multiple
> > times
> > and how to deal with it?
>
> That does sound odd to me
9 GB?
4. How to optimise the repository to cut the size down further?
My next step is to somehow push the fat pig into GitHub, Bitbucket or
Azure DevOps ;-)
I've used Git for a few years, but I'm pretty newbie regarding low-level
or administration tasks, so I might have made basic err
26 matches
Mail list logo
