meaningfully checked out, the repo's data is just stale and no
longer reflects reality.
This makes it so that if nothing is present where a worktree is
supposedly checked out, deleting the branch will automatically prune it.
Signed-off-by: Peter Jones
---
builtin/branch.c | 6 +-
1 fi
Add the function is_worktree_locked(), which is a helper to tell if a
worktree is locked without having to be able to modify it.
Signed-off-by: Peter Jones
---
builtin/worktree.c | 2 +-
worktree.c | 16
worktree.h | 5 +
3 files changed, 22 insertions
ingfully checked out, the repo's data is just stale and no longer
reflects reality.
This makes it so that if nothing is present where a worktree is
supposedly checked out, and it is not locked, we ignore that the
worktree exists, then it should be cleaned up.
Signed-off-by: Peter Jones
---
br
Add delete_worktrees_dir_if_empty() and prune_worktree() to the public
API, so they can be used from more places. Also add a new function,
prune_worktree_if_missing(), which prunes unlocked worktrees if they
aren't present on the filesystem.
Signed-off-by: Peter Jones
---
builtin/workt
e "git worktree lock". What bugs me though, is
that using worktrees basically means I have to replace fairly regular
filesystem activities with worktree commands, and it doesn't seem to be
*necessary* in any way. And I'm going to forget. A lot.
To me, there doesn't seem to be any reason these need to behave any different:
$ git worktree add foo foo
$ rm -rf foo
vs
$ git worktree add foo foo
$ git worktree remove foo
And in fact the only difference right now, aside from some very
minuscule storage requirements that haven't gotten cleaned up, is the
first one leaves an artifact that tells it to give me errors later until
I run "git worktree prune" myself.
I'll send another revision of this patchset as a reply to this mail,
which should clear up some of our differences.
--
Peter
rom libgit
currently.)
Signed-off-by: Peter Jones
---
branch.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/branch.c b/branch.c
index 579494738a7..60322ded953 100644
--- a/branch.c
+++ b/branch.c
@@ -360,6 +360,9 @@ void die_if_checked_out(const char *branch, int
ignor
meaningfully checked out, the repo's data is just stale and no
longer reflects reality.
This makes it so that if nothing is present where a worktree is
supposedly checked out, deleting the branch will automatically prune it.
Signed-off-by: Peter Jones
---
builtin/branch.c |
email: peterhecto...@outlook.com
Management
Mr Peter Hector
email: peterhecto...@outlook.com
Management
Mr Peter Hector
?Kjaere postkassebruker
Du har mottatt denne e-postmeldingen fordi kontoen din er brukt fra et annet
sted av deg eller noen andre. vi har mandat til a apne en etterforskning av
denne saken. For a beskytte kontoen din, vennligst se lenken nedenfor for en
oyeblikkelig oppdatering for a sikre kont
?Kjaere postkassebruker
Du har mottatt denne e-postmeldingen fordi kontoen din er brukt fra et annet
sted av deg eller noen andre. vi har mandat til a apne en etterforskning av
denne saken. For a beskytte kontoen din, vennligst se lenken nedenfor for en
oyeblikkelig oppdatering for a sikre kont
e happy with a parameter and/or configuration variable saying
"amend and rebase uses last commit date".
--
\\// Peter - http://www.softwolves.pp.se/
the date of the last fixup'ed or squash'ed commit
would probably be better.
--
\\// Peter - http://www.softwolves.pp.se/
rustrating.
Yours,
Peter
mailto:g...@ptoye.com
www.ptoye.com
In a perforce setup where login is not required, communication fails
because p4_check_access does not understand the response from the p4
client. Fixed by detecting and ignoring the "info" response.
Signed-off-by: Peter Osterlund
---
git-p4.py | 2 ++
1 file changed, 2 insertion
7;login' not nece|
0040 73 73 61 72 79 2c 20 6e 6f 20 70 61 73 73 77 6f |ssary, no passwo|
0050 72 64 20 73 65 74 20 66 6f 72 20 74 68 69 73 20 |rd set for this |
0060 75 73 65 72 2e 30 |user.0|
0066
Best regards,
--
Peter Osterlund - peterosterlu...@gmail.com
http://hem.bredband.net/petero2b
On 12/27/18 3:55 PM, Jonathan Nieder wrote:
> Hi,
>
> H. Peter Anvin wrote:
>
>> [merge "version"]
>> name = Version file merge driver
>> driver = sort -V -r %O %A %B | head -1 > %A.tmp.1 && mv -f %A.tmp.1
>> %A
&g
The current definition for merge drivers require the output file %A to be
overwritten. When using a pipeline of Unix commands, this often results in %A
being truncated too early, requiring the user to add a temporary file managed
explicitly.
It would be far preferable if git could manage this; per
Right now, merge rules can get selected in .gitattributes, which is
version-controlled. However, there does not appear to be any way to *define*
custom merge rules which is version controlled.
There are a lot of different files which can benefit from custom merge rules,
especially ones that are in
I am pleased to announce the release of Stacked Git 0.19.
The big feature for this release is Python 3 support, but 0.19 also
contains some important bug fixes and more robust test infrastructure.
The full release notes follow.
Cheers,
Pete
%<
Stacked Git 0.19 re
Good point. I'll check it out. Thanks for the tip.
Thanks,
Peter
Thanks,
Peter Kostyukov
Senior Systems Engineer
Kohl's Department Stores - KIC
Office: 262-703-6533
On Sat, Nov 3, 2018 at 6:48 PM Philip Oakley wrote:
>
>
> On 03/11/2018 16:44, brian m. carlson wrote:
>
e any configuration setting that can disable this git's
behavior or is there any other workaround without allowing Internet
access? Otherwise, every git command run on a server without the
Internet takes about 30 seconds to complete.
Please advise.
Thanks,
Peter
CONFIDENTIALITY NOTICE:
; I'm sure we'll see patches from them, since after all, they would not
Why should they be concerned? They can rewrite history if necessary.
They have a solution, though an inconvenient one. As far as the lawyers
are concerned, that solution is pefectly fine.
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
as well as part of
> their purchase of Github.
So? If a thousand lawyers claim 1+1=3, it becomes a mathematical truth?
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
so you can get github and gitlab to get rid of the information.
> But it's *pointless*.
It's up to the subject to consider it pointless or not to exercise his
rights...
> Your problem is in the word: "a"
...and against whom, whether one repository provider, the major ones,
all of them he can find.
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
is line
> of argument wouldn't work.
As I already stressed, having an interest is not enough. You need to
have overriding legitimate grounds.
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
or publishing; the GDPR calls it
"disclosure (Art. 4 (2) GDPR) to an unspecified number of unspecified
recipients (Art. 4 (9) GDPR), including ones in third countries
(Chapter 5) in a repetitive (Art 49 (1) GDPR) fashion".
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
ies is in the thousands.
In practical terms, if someone wishes to exercise his right to be
forgotten, he will usually send the request to the maintainer and stop
him from distributing the information, and perhaps to a third party he
might use as a platform for publication, such as github.
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
t; revealing this license granting data, not me.
It prohibits publishing, and only after a request to be forgotten. It
does not prohibit storing your private copy.
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
copy of the metadata, your probably have
overriding legitimate grounds, however.
The GDPR is not an "all or nothing" thing.
Facebook and Google certainly do not have overriding legitimate grounds
for most of the data they keep privately.
Is it that so hard to understand?
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
d stay public, or you start off private and
> stay there.
Nope. The GDPR says you have to go from public to private if the
subject wishes so and there are no overriding legitimate grounds.
That is the entire purpose of the GDPR's right to be forgotten.
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
GDPR compliant.
It might be possible to implement my solution without changing git,
btw. Simply use the anonymous hash as author name, and store the random
number and the author as a git-notes. git-notes can be rewritten or
deleted at any time without changing the commit ID. I am currently
looking into this solution. One just needs to add something that can
verify and resolve those anonymous hashes.
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
w those, or anything but git clone (and even that only
if author verification is requested) could possibly be affected in any
significant way.
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
Just give me a lot of
money."
Having the ability to validate yet erase data form repositorys is
desirable from a technical point of view. It has a lot of uses, not
necessarily only legal ones. The objection of efficiency raised by Ted
is a valid one. The strawman argument is not.
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
sclaimers and such
for enormous sums of money. In a lot of companies. To "solve" a
technical issue by pseudo-legal means by finding excuses for why the
"right to be forgotten" doesn't have to be implemented in specific
cases such as git. What if all that lawyer mone
x27;t see any
obvious criticism leading to complete rejection of the approach.
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
7;s
pseudonymization, not anonymization. You need to ensure a different
hash in each instance, and you need to ensure there's no easy way to
reconstruct the data from its hash. Hence $random_number (or let's call
it $huge_random_number, it should have x bits if the hash has x bits).
If
to be forgotten, or simply discuss technical changes for git
which enable its easy implementation, without legal excuses for not
doing supporting it?
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
on control such that it is
more in line with the GDPRs idea that people have a right to be
forgotten, but to also be useful for a multitude of other applications.
The lawyers can then build on this.
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
depending on how it is implemented.
What do you think about my proposal as a solution for the problem?
You provide a lot of arguments about why it is not a necessity to have
this, but let's assume it is; is there any actual problem you see with
the proposal, except that someone would have to implement it?
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
gets several fines for this by EU
authorities but ignores them and doesn't pay them, and the CEO one day
takes a flight to Frankfurt to continue by train to Switzerland to get
some cash from his bank account, then he will most likely not reach
Swiss territory.
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
There is an old German proverb, warning that even
humorous trolling might be dangerous: "Man soll den Teufel nicht an die
Wand malen!" ;)
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
) and thus
not covered by the GDPR. The history could still be completely
verified, and when displaying the log, the erased entry could be
displayed as "<>".
What do you think about this?
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
On 4 May 2018 at 14:26, Cornelia Huck wrote:
> On Fri, 4 May 2018 08:07:53 -0500
> Eric Blake wrote:
>> On the other hand, cc'ing all recipients for a largely mechanical patch
>> series that was split into 67 parts, in part because it touches so many
>> different maintainers' areas, may make the
means Art. 6 (1) lit. b wouldn't apply anymore and
you'd have the same issue as with consent-based processing of the
information (lit. a).
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
ws.ycombinator.com/item?id=16509755
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
On 2018-03-28 00:56, Stefan Beller wrote:
> On Tue, Mar 27, 2018 at 12:55 PM Peter Oberndorfer
> wrote:
Hi,
as expected your patch fixed the BUG output.
Thanks!
>> 2) Should "git submodule deinit" work on submodules that were removed by
> upstream already?
>
>
m already?
For more debugging information please see below.
Thanks,
Greetings Peter
~/src/rust/rust$ git --version
git version 2.17.0.rc1.47.g9f57127417.dirty
(this should basically be 90bbd502d54fe920356fa9278055dc9c9bfe9a56 + some
Makefile adjustments)
Git Gui reports
src/rt/hoedown
Untracke
0xff)
+return 1;
+ return 0;
+}
This would also match a UTF-32LE BOM, not that I think anyone would
actually use that for text files, but it might be worth adding a test
for that, just in case?
if (text[0] == 0xff && text[1] == 0xfe)
return len < 4 || (text[2] != 0 &a
lot of those systems today, but those who used to use
the 'right' timestamps might for legacy reasons explicitly configure
their system to use those timezone variants. I personally did this for
a number of years, but then converted the filesystems timestamps to
'posix' and I am now exclusively using 'posix' ones.
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
I'm still not sure whether it will be a UNIX-format timestamp or
whether a human-readable date/time might be preferrable.
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
ve...).
Well, Johannes's proposed solution seems pretty reasonable and
realistic to me. Thanks to Phillip's hint about unquote_path() in
Git.pm it seems I now have all the needed ingredients to implement this
feature.
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
as you'd get if git's tree format would change
> to include mtimes (which isn't going to happen), but with a lot more
> flexibility.
Well, from basic logic, I don't see how a decision not to implement a
feature could possibly increase flexility. The opposite seems to be the
case.
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
On Tue, Feb 20, 2018 at 11:32:23PM +0100, Johannes Schindelin wrote:
> Hi Peter,
>
> On Tue, 20 Feb 2018, Peter Backes wrote:
>
> > On Tue, Feb 20, 2018 at 11:46:38AM +0100, Johannes Schindelin wrote:
> >
> > > I would probably invent a file format (``)
&g
it were not for the build tool issues, git would have
tracked mtime from the very start.
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
t cat-file -p master^{tree}
Perhaps I got it wrong.
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
the principle of least
astonishment.
What bugs me is my impression from the FAQ that even as an option, the
feature might be unwelcome.
Best wishes
Peter
--
Peter Backes, r...@helen.plasma.xg8.de
reserve mtimes, but that this code was
removed because of the build tool issues. Perhaps that code could
simply be put back in, and surrounded by conditions.
Best wishes
Peter
PS: Given the opportunity, I want to thank you very much for
maintaining the git repository for my cvsclone to
Please provide options to store and restore modification times. It
shouldn't be hard to do, given that other metadata such as the mode is
already stored. It would make live so much easier. And the fact that
this has made into the FAQ clearly suggests that there are many others
who think so
r/software/aix/linux/toolbox/alpha.html
It's git 2.12.0, so it's not the very latest version of git, but it's
not bad for AIX.
Peter Harris
directly on my
private mailbox: peterddeng2...@secsuremailer.com and let me know if you got
the proposal and if you are interested in working with me to accomplish the
proposed project.
I await your response on my private mailbox above.
Regards,
Peter.
peterddeng2...@secsuremailer.com
Greeting
In a brief introduction, I am a lawyer Meinze klaus peter,from Germany
but now i lives in London, I sent you an email about your deceased
relative, but I have not received any response from you, deceased is a
citizen of your country with the same surname with you, he is an
exporter
Just wondering if I submitted this patch correctly and to the right place.
On 11/12/17 11:48, Peter Urbanec wrote:
When pushing changes, the Remote combobox for the Destination Repository
does not take all available space in the layout. With long remote names,
this causes the combobox to have
"In einer kurzen Einführung,
Ich bin ein Rechtsanwalt Meinze Klaus Peter, aus Deutschland, lebe ich
in London, habe ich Ihnen eine E-Mail über meine verstorbene Familie
geschickt, aber ich habe keine Antwort von Ihnen erhalten, der
Verstorbene ist ein Bürger in Ihrem Land mit dem gle
of the grid
cell and use the same padding as url_t for a consistent, dynamic layout.
Signed-off-by: Peter Urbanec
---
lib/transport.tcl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/transport.tcl b/lib/transport.tcl
index a1a424a..1046dc5 100644
--- a/lib/transport.tcl
/bin/git cherry-pick
-x 717eb328940ca2e33f14ed27576e656327854b7b
[redacted 19be3551bc] Redacted
Author: Redacted
Date: Mon Oct 16 15:58:05 2017 +0200
1 file changed, 2 insertions(+), 2 deletions(-)
real0m15,345s
user0m14,908s
sys 0m0,528s
Thanks!
--
\\// Peter - http
t. Is there a public repo where I can pull
these patches from instead of trying to apply them manually, as there
are several patch series involved here?
--
\\// Peter - http://www.softwolves.pp.se/
:58:05 2017 +0200
1 file changed, 2 insertions(+), 2 deletions(-)
real0m15,473s
user0m14,904s
sys 0m0,488s
I'll add this setting for the repository for the future, thank you!
--
\\// Peter - http://www.softwolves.pp.se/
ith Ctrl+C
(neither when running from the command line, nor when running inside
gdb). It didn't finish in the 20 minutes I gave it.
I also tried with diff.renames=false, which also seemed to fail.
--
\\// Peter - http://www.softwolves.pp.se/
git.c:554
#14 0x55567cf6 in run_argv (argv=0x7fffe0e0,
argcp=0x7fffe0ec) at git.c:606
#15 cmd_main (argc=, argv=)
at git.c:683
#16 0x55566e01 in main (argc=4, argv=0x7fffe318)
at common-main.c:43
--
\\// Peter - http://www.softwolves.pp.se/
I thought it was just updating the status, but "git status" returns
immediately, while cherry-picking takes several minutes for every
cherry-pick I do.
--
\\// Peter - http://www.softwolves.pp.se/
'' In einer kurzen Einführung,
Ich bin ein Rechtsanwalt Meinze Klaus Peter, aus Deutschland, lebe
zurzeit in London, ich habe dir eine E-Mail über deine verstorbene
Familienangehörige verspätet. Ich habe keine Antwort von dir erhalten.
Die verstorbene Person ist eine Bürgerin deines
"In einer kurzen Einleitung,
Ich bin ein Anwalt Meinze Klaus peter, aus Deutschland, ich lebe
Zurzeit in London, schickte ich Ihnen eine E-Mail über Ihren
Verstorbenen Familienmitglied Spätfamilie, ich habe keine Antwort von
Ihnen erhalten verstorben ist ein Bürger in deinem Land mit dem
gle
t that probably wouldn't have helped if I had put
this in my global config).
--
\\// Peter - http://www.softwolves.pp.se/
I did try to test that hypothesis by editing the filter to be a no-op,
but it's possible I go that wrong. My apologies for bugging the list!
On 11 July 2017 at 00:06, Jeff King wrote:
> On Tue, Jul 11, 2017 at 06:15:17AM +0200, Torsten Bögershausen wrote:
>
>> On 11/07/17 01:45
x27;s an example of the behaviour, with "git reset --hard" failing to
clear a diff in the index:
https://paste.debian.net/975811/
Happy to collect additional debugging information if it's useful.
--
Peter
"zip64 format" or not. It seems a bit hit or
miss to me, the best would be to always use the pre-amble descriptor,
but that requires holding the entire compressed data in memory (or
using temporary files or running two passes), neither which are very
good ideas.
--
\\// Peter - http://www.softwolves.pp.se/
ality, I guess)?
OK, so only enable zip64 mode if there are files >4G or the archive
ends up being >4G. But the question is how we can tell, especially in
streaming mode, and especially if data descriptors are magical...
--
\\// Peter - http://www.softwolves.pp.se/
le to read them anyway if
there are no overflowing fields, right? And, besides, who in 2017 has
an unzip tool that is unable to read zip64? Info-Zip UnZip has
supported Zip64 since 2009.
--
\\// Peter - http://www.softwolves.pp.se/
enever it has any ZIP64
structures.
--
\\// Peter - http://www.softwolves.pp.se/
be a zip64 record with the actual size (even if it is
0x).
Also set the version required to 45 (4.5) for any record that has zip64
fields.
--
\\// Peter - http://www.softwolves.pp.se/
ze,
compressed size, and the offset to the local header when they
overflow 4GB.
At least that makes it easier to construct, as we only have one
central directory and can just extend the records that need extending.
Will fix soon.
--
\\// Peter - http://www.softwolves.pp.se/
is dynamic.
That is what I was trying to figure out, APPNOTE is extremely vague on
the subject, but thinking back I recall that you are correct.
--
\\// Peter - http://www.softwolves.pp.se/
not
quite sure what it is supposed to store. I need to investigate that
further, I assume.
--
\\// Peter - http://www.softwolves.pp.se/
If the size of the files in the archive cannot be expressed in 32 bits, or
the offset in the zip file itself, add zip64 local headers with the actual
size. If we do find such entries, we also set a flag to force the creation
of a zip64 end of central directory record.
Signed-off-by: Peter
If the size of the files in the archive cannot be expressed in 32 bits, or
the offset in the zip file itself, add zip64 local headers with the actual
size. If we do find such entries, we also set a flag to force the creation
of a zip64 end of central directory record.
Signed-off-by: Peter
Using git-gui on systems that run a TK version below 8.6.0 results in a
crash when checking for the current theme.
Catch the error on those systems and use a different command to check
for the current theme.
Signed-off-by: Peter van der Does
---
lib/themed.tcl | 6 +-
1 file changed, 5
Using git-gui on systems that run a TK version below 8.6.0 results in a
crash when checking for the current theme.
Catch the error on those systems and use a different command to check
for the current theme.
---
git-gui/lib/themed.tcl | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
di
ank you very much for your time,
> David
>
It looks like the git gui needs TCL/TK 8.6.0 or higher. Since that
version the command 'ttk::style theme use' has been changed, which
allows the command to be run without an argument and then returning the
current theme used.
I beli
the
limit of sane use. Perhaps not, perhaps the user likes to use two
different frontends which use different GnuPG versions as their backend.
Luckily, expiration extensions are picked up by just transferring the
public key part of a secret key, so that does work.
Peter.
--
I use the GNU Privacy Guar
Ctrl+T/Ctrl+U add/remove only one file, not the whole selection - used
to work. Neither are access keys for menu underlined (Ease of access
center > underline keyboard shortcuts is on), so there is no way to
effectively work with keyb only.
git-gui verison 0.21 GITGUI
git version 2.11.1.windows.
winning ticket(1).docx
Description: MS-Word 2007 document
Hi,
Junio C Hamano wrote:
> Peter Law writes:
>
>>> Teach git-completion.bash about the 'diff' option to 'git diff
>>> --submodule=', which was added in Git 2.11.
>>
>> I posted this patch back in December, but I've not heard anything
ong it usually takes to get a response to patches? (also whether I'd
gotten some part of the submission process wrong?)
Thanks,
Peter
further discussion.
I anticipate your response.
Sincerely,
Peter Karl.
Tel: +447012937022 | Fax: +448458743257
s will be made invalid in upcoming
releases. please use . instead if you meant to match all paths"
message.
- I expected no warning message since I included a "." with my original command.
I believe that I should not be seeing this warning message as I
included the requested "." pathspec.
~ Peter Urda
http://urda.cc
I've just upgraded to macOS 10.12.1 and now I can't paste into git-gui
(the commit message box).
It seems to work if the text is copied from within git-gui but not from
outside. I've tried using the latest dmg from
https://git-scm.com/download/mac (2.10.1) but it doesn't fix the problem.
On 27/10/16 09:59, Junio C Hamano wrote:
Stefan Beller writes:
- We have to make separate commits and manage corresponding topic
branches for the superproject and subprojects.
Well yeah, that is how submodule work on a conceptual level.
While having multiple commits may seem like overhead, n
It seems that git gui does not adhere to the config settings
git config commit.gpgsign true
git config --global user.signingkey
Commits done through git gui are not signed while done through cli they
are signed
Peter van der Does
--
To unsubscribe from this list: send the line "unsubscrib
1 - 100 of 366 matches
Mail list logo
