Am Thu, 5 Apr 2018 12:32:27 -0400
schrieb Jeff King :
> The general strategy in Git's config is that instead of "unsetting", you
> should overwrite with whatever value you _do_ want. So a config option
> like sendemail.smtpauth should accept some kind of empty or "none" value
> to disable auth.
>
Am Thu, 05 Apr 2018 13:21:02 +0200
schrieb Ævar Arnfjörð Bjarmason :
> I'm assuming you mean something like:
> [user]
> # This is an error
> -email
Yes. Just some flag to say "whatever value this variable has from earlier
parsing, forget it in case it really exists". Just
Am Thu, 05 Apr 2018 10:42:15 +0200
schrieb Ævar Arnfjörð Bjarmason :
> I've been meaning to work on this but haven't figured out a good syntax for
> it (suggestions welcome!).
Just prefix the knob with something like "no." or "-" or whatever to indicate
that it never happened.
Olaf
pgpfQgIWe
My ~/.gitconfig looks like this, because all cloned repositories require these
settings:
[sendemail]
from = Olaf Hering
envelopesender = o...@aepfle.de
chainreplyto = false
ccover = yes
smtpencryption = tls
smtpdomain = sender
smtppass
I think send-email should understand all options of format-patch.
At least for '-v n' this fails, one has to type '--reroll-count n' as a
workaround with git version 2.13.3:
+ git send-email -v 2 --annotate --confirm=always
--to-cmd=scripts/get_maintainer.pl 'HEAD^'
fatal: ambiguous argument '2':
On Tue, Feb 14, Olaf Hering wrote:
> How would I debug it?
One line is supposed to be longer than 998 chars, but something along
the way truncated it and corrupted the patch. No idea why the error
today is different from the error yesterday.
'git pull' has to be used in thi
Am Tue, 14 Feb 2017 12:40:36 -0800
schrieb Junio C Hamano :
> Olaf Hering writes:
>
> > How is git send-email and git am supposed to handle a text file
> > which lacks a newline at the very end? This is about git 2.11.0.
>
> I think this has always worked, though.
How is git send-email and git am supposed to handle a text file which
lacks a newline at the very end? This is about git 2.11.0.
Right now the patch in an email generated with 'git send-email' ends
with '\ No newline at end of file', which 'git am' can not handle. To
me it looks like whatever var
Hey, asciidoc made a move, so this patch is good to go:
https://github.com/asciidoc/asciidoc/pull/9
Thanks.
Olaf
On Tue, Feb 10, Jeff King wrote:
> On Tue, Feb 10, 2015 at 04:17:47PM +0100, Olaf Hering wrote:
>
> > On Fri, Jan 30, Jeff King wrote:
> >
> > > I ha
On Thu, Aug 18, Jeff King wrote:
> Olaf, what version of patch are you using?
Mostly 2.7.x, but also add 2.5.x to the mix.
So far I did not try what the tools dealing with the resulting patch
file would actually do with such a stripped down variant.
Olaf
signature.asc
Description: PGP signatur
This command used to create a diff which can be consumed by patch. But
at least with 2.9.3 it just gives a rename output:
git format-patch \
--no-signature \
--stdout \
--break-rewrites \
--keep-subject \
95fa0405c5991726e06c08ffcd8ff872f7fb4f2d^..95fa0405c599172
On Thu, Apr 21, John Keeping wrote:
> $ git tag --contains aed06b9cfcabf8644ac5f6f108c0b3d01522f88b
Thanks for that, I did not know this variant.
Unless git does not do it for me, I may hackup my script like that to
find the earlierst tag:
for i in `git tag --contains aed06b9cfcabf8644ac
On Thu, Apr 21, Matthieu Moy wrote:
> My guess is that this commit has been sitting for a long time in a
> repo outside Linus' linux.git, and got merged only recently.
Thats what it looks like. And thats what I'm complaining about. But in
fact that file is there since v3.13-rc7 (if the tag is rea
To track the changes in hyperv related files I created some scripts
years ago to automate the process of finding relevant commits in
linux.git. Part of that process is to record the tag when a commit
appeared in mainline. This worked fine, until very recently.
Suddenly years-old commits are declar
To which branch was this applied?
Its still broken in git-2.6.0.
Olaf
On Fri, May 01, Pat Thoyts wrote:
> René Scharfe writes:
>
> >Looping in Pat (git-gui maintainer).
> >
> >Am 15.04.2015 um 09:22 schrieb Olaf Hering:
> >> Ping?
> >>
> >>
Am 08.09.2015 um 13:28 schrieb Ævar Arnfjörð Bjarmason:
> Yes, format-patch is written in C, but you mentioned send-email, which
> is a Perl script.
send-mail is handled in my copy of the bash_completion, at the end
the list the format-patch options gets appended. That list could be
autogenerated
Am 07.09.2015 um 17:34 schrieb Ævar Arnfjörð Bjarmason:
> On Mon, Sep 7, 2015 at 5:07 PM, Olaf Hering wrote:
>> https://github.com/libguestfs/libguestfs/commit/0306c98d319d189281af3c15101c8d343e400f13
>
> This is an interesting approach, but wouldn't help with git-send-e
"git send-email --f" lacks --find-renames and others. Is the list
of possible options maintained manually? Perhaps this should be
automated by placing the long strings in an ELF section, then filling
variables like $__git_format_patch_options from such ELF section.
An example how this was done in l
On Tue, Jul 14, John Keeping wrote:
> It was added in an evil merge (f9da455b93f6ba076935b4ef4589f61e529ae046),
> try:
>
> git log -p -M --stat --cc -- drivers/hv/channel_mgmt.c
Thanks. Thats rather useless output...
@@@ -404,7 -365,7 +404,7 @@@ static u32 next_vp
* performance critic
I wonder why this command fails to show all commits that modify a given
function:
linux.git $ git log -p -M --stat -- drivers/hv/channel_mgmt.c
With commit 1f656ff3fdddc2f59649cc84b633b799908f1f7b init_vp_index() has
"const uuid_le *type_guid" already. And somewhere between commit
d3ba720dd58
Ping?
On Tue, Feb 10, Olaf Hering wrote:
> Ping?
>
> On Mon, Jan 26, Olaf Hering wrote:
>
> > ALL_LIBFILES uses wildcard, which provides the result in directory
> > order. This order depends on the underlying filesystem on the
> > buildhost. To get reproducible
On Fri, Mar 20, Junio C Hamano wrote:
> Olaf Hering writes:
>
> > What does it take to send the cover letter to all people which are
> > listed in the Cc: list of the following patches? Each patch has a
> > different Cc: list. The "git send-email --help" comm
What does it take to send the cover letter to all people which are
listed in the Cc: list of the following patches? Each patch has a
different Cc: list. The "git send-email --help" command suggests that
this cmdline should do it. But the cover letter goes just to the address
listed in --to=:
env
On Fri, Jan 30, Jeff King wrote:
> I have 8.6.9-3 installed (it is part of Debian testing/unstable now),
> and confirmed that:
>
> diff --git a/Documentation/asciidoc.conf b/Documentation/asciidoc.conf
> index 2c16c53..10c777e 100644
> --- a/Documentation/asciidoc.conf
> +++ b/Documentation/ascii
Ping?
On Mon, Jan 26, Olaf Hering wrote:
> ALL_LIBFILES uses wildcard, which provides the result in directory
> order. This order depends on the underlying filesystem on the
> buildhost. To get reproducible builds it is required to sort such list
> before using them.
>
> S
On Tue, Jan 27, Junio C Hamano wrote:
> Olaf Hering writes:
>
> > Several files in Documentation have an unstable 'Last updated' timestamp.
> > The
> > reason is that their mtime changes every time, which prevents reproducible
> > builds.
> >
On Mon, Jan 26, Olaf Hering wrote:
> Several files in Documentation have an unstable 'Last updated' timestamp. The
> reason is that their mtime changes every time, which prevents reproducible
> builds.
>
> 341 technical/api-index.txt: technical/api-index-skel.txt \
&g
Several files in Documentation have an unstable 'Last updated' timestamp. The
reason is that their mtime changes every time, which prevents reproducible
builds.
341 technical/api-index.txt: technical/api-index-skel.txt \
342 technical/api-index.sh $(patsubst %,%.txt,$(API_DOCS))
343
ALL_LIBFILES uses wildcard, which provides the result in directory
order. This order depends on the underlying filesystem on the
buildhost. To get reproducible builds it is required to sort such list
before using them.
Signed-off-by: Olaf Hering
---
git-gui/Makefile | 2 +-
1 file changed, 1
On Fri, Nov 14, Andreas Schwab wrote:
> Olaf Hering writes:
>
> > Even if I do a fresh clone with --bare, the result can not be updated
> > anymore with git fetch. What I'm doing wrong?
>
> A --bare clone has no connection to its origin (there are no remotes).
On Thu, Nov 13, Fredrik Gustafsson wrote:
> That's one of the reason it's not recommended to push into a non-bare
> repository. You should clone your repo-master with the --bare option to
> avoid having a work dir there.
Even if I do a fresh clone with --bare, the result can not be updated
anymor
On Fri, Nov 14, Olaf Hering wrote:
> On Fri, Nov 14, Fredrik Gustafsson wrote:
>
> > On Fri, Nov 14, 2014 at 11:14:27AM +0100, Olaf Hering wrote:
> > > So my repo-master is now "bare". I pushed from repo-branchA into
> > > repo-master and see my commits in
On Fri, Nov 14, Fredrik Gustafsson wrote:
> On Fri, Nov 14, 2014 at 11:14:27AM +0100, Olaf Hering wrote:
> > So my repo-master is now "bare". I pushed from repo-branchA into
> > repo-master and see my commits in both repos. But pushing from
> > repo-master to the r
On Thu, Nov 13, Fredrik Gustafsson wrote:
> Thanks for sharing your notes! A few comments:
>
> On Thu, Nov 13, 2014 at 04:44:57PM +0100, Olaf Hering wrote:
> > First clone the remote repository as usual. Then create a local branch for
> > each remote branch that is sup
On Thu, Nov 13, Olaf Hering wrote:
> So how can I reduce the disk usage needed for the four .git dirs above?
> I looked around in the docs that came with my git-2.1.3 package, but
> found nothing that answers my question. Maybe we can workout something
> and add it to one of the e
On Thu, Nov 13, Roger Gammans wrote:
> Note the first sentence of the second paragraph.
> eg:
> # git clone git://host/repo.git repo-master
> # git clone repo-master repo-branchA
> # cd repo-branchA
> # git checkout -b branchA origin/branchA
It fails right here because in this dir only "mast
On Thu, Nov 13, Fredrik Gustafsson wrote:
> On Thu, Nov 13, 2014 at 12:14:44PM +0100, Olaf Hering wrote:
> >
> > How can I reduce the disk usage for multiple copies of the same repo?
>
> You can use --local och --shared. As you say --shared can be dangerous.
> If you
How can I reduce the disk usage for multiple copies of the same repo?
Up to now I just made copies like this, but since .git alone is already
2GB it becomes expensive:
# git clone git://host/repo.git repo-master
# cp -a repo-master repo-branchA
# cd repo-branchA
# git checkout -b branchA ori
On Wed, Oct 08, Jens Lehmann wrote:
> Okay, I just checked that xen doesn't use submodules but uses simple
> embedded repos ignored by the .gitignore file. From a quick glance
> it looks like handling the sub projects is scripted in the Makefiles.
> This is perfectly fine, but then you can't reall
On Wed, Oct 08, Jens Lehmann wrote:
>git foo && git submodule foreach --recursive git foo
Looks like a submodule is yet another thing, or I have to learn what a
submodule is:
olaf@bax:~/xen $ find . -name .git
./.git
./tools/qemu-xen-dir-remote/.git
./tools/qemu-xen-traditional-dir-remote/.g
How can I teach 'git grep $string' to also consider subprojects?
The build system of xen.git clones 4 other trees into a directory in its
source tree during build. It would be nice if my 'git grep' searches
also in these cloned subdirs. Somehow there must be some knowledge
because 'git clean -dfx
What is the correct syntax/setup to push from one remote to another?
I did something like this, to feed a github repo:
# rm -rf $$
# mkdir $$
# cd $$
# git --init
# git remote add --tags t
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
# git remote add --tags o g...@github
There is an incorrect message when doing "git rebase -i remote/branch".
I have it only in german, see below. what happend is:
#01 make changes on another host
#02 copy patchfile to localhost
#03 apply patchfile
#04 git commit -avs # create commit#1
#05 sleep 123456
#06 make different changes on a
43 matches
Mail list logo
