[BUG] Branches before "git subtree add --squash" are pushed via "git subtree push"

2019-07-15 Thread Danny Lin
Say we have a repository with "master" and "sub" branches like below: A---B---C---D---E---F master / X---Y X---Y sub where commits A and B include changes in subdirectory "sub", commit C removes subdirectory "sub", commit D is generated by "git subtree add -P s

[PATCH v2 0/1] status: remove the empty line after hints

2019-06-04 Thread John Lin via GitGitGadget
empty lines even if hints are presented. John Lin (1): status: remove the empty line after hints t/t7060-wtstatus.sh| 5 t/t7508-status.sh | 62 -- t/t7512-status-help.sh | 14 -- wt-status.c| 4 --- 4 files changed, 85 dele

[PATCH v2 1/1] status: remove the empty line after hints

2019-06-04 Thread John Lin via GitGitGadget
From: John Lin Before this patch, there is inconsistency between the status messages with hints and the ones without hints: there is an empty line between the title and the file list if hints are presented, but there isn't one if there are no hints. This patch remove the inconsisten

[PATCH 1/1] status: remove the empty line after hints

2019-05-15 Thread John Lin via GitGitGadget
From: John Lin Before this patch, there is inconsistency between the status messages with hints and the ones without hints: there is an empty line between the title and the file list if hints are presented, but there isn't one if there are no hints. This patch remove the inconsisten

[PATCH 0/1] status: remove the empty line after hints

2019-05-15 Thread John Lin via GitGitGadget
empty lines even if hints are presented. John Lin (1): status: remove the empty line after hints t/t7060-wtstatus.sh| 5 t/t7508-status.sh | 62 -- t/t7512-status-help.sh | 14 -- wt-status.c| 4 --- 4 files changed, 85 dele

[PATCH v2] status: add an empty line when there is no hint

2019-04-29 Thread John Lin
ve case and some similar cases. Signed-off-by: John Lin --- t/t7500-commit-template-squash-signoff.sh | 1 + t/t7508-status.sh | 5 + t/t7512-status-help.sh| 1 + wt-status.c | 12 4 files changed, 15 inser

[PATCH] status: add an empty line when there is no hint

2019-04-23 Thread John Lin
ve case and some similar cases. Signed-off-by: John Lin --- wt-status.c | 12 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/wt-status.c b/wt-status.c index 445a36204a..0766e3ee12 100644 --- a/wt-status.c +++ b/wt-status.c @@ -175,7 +175,7 @@ static void wt_longstatu

Gute Nachrichten

2018-05-02 Thread Sgt Monica Lin Brown
Ich bin Sgt.Monica Lin Brown, ursprünglich aus Lake Jackson Texas USA. Ich habe persönlich eine spezielle Recherche im Internet durchgeführt und bin auf Ihre Informationen gestoßen. Ich sende Ihnen diese E-Mail von der US-Militärbasis Kabul Afghanistan. Ich habe einen gesicherten

[no subject]

2018-04-21 Thread LiN JiNG
I didn't get any reply from you concerning my last email.. Br LiN __ Sky Silk, http://aknet.kz

New Order

2018-02-03 Thread Lin.
Dear git@vger.kernel.org How are you? We are in need of your products/service, Kindly send us your FOB and MOQ so that we can place our order. The order will deliver in Taiwain branch Looking forward to your respond asap. Best Regards, Lin Tou Prime Success Co. Ltd Address: Av. Praia Grande

UTF-8-safe way for char-level-diff

2018-01-19 Thread Danny Lin
Git has a diff.wordRegex config that allows the user to specify a regex that defines a word. Setting diff.wordRegex to "." works well for a char-level diff for ASCII chars, but not for UTF-8 chars. For example, if a file (encoded by UTF-8) with text "一人" is changed to "丁人", "git diff --word-diff=c

Re: [PATCH] contrib/subtree: fix linefeeds trimming for cmd_split()

2015-05-06 Thread Danny Lin
7; or 'git checkout' Maybe using printf is the way to go? 2015-05-06 3:11 GMT+08:00 Junio C Hamano : > Danny Lin writes: > >>> I think this was written knowing that "say" is merely a thin wrapper >>> of "echo" (which is a bad manner but happen

Re: [RFC PATCH] diff: do not use creation-half of -B as a rename target candidate

2015-02-01 Thread Yue Lin Ho
A1 = "I am file A." B1 is copied from A1, so B1 = "I am file A." B1 changes to B2 = "I am file B." A1 changes to A2 = "file A is changed a lot, a lot, ..., a lot." At this moment, commit A2 and B2 files. -- View this message in context: http://git.661346.n2.nabble.com/Git-BUG-Please-do-not-us

Re: Upgrade Git in openSUSE13.1

2014-12-24 Thread Yue Lin Ho
or http://sourceforge.net/projects/git-osx-installer/files/ for OS X users see https://blog.heroku.com/archives/2014/12/24/update_your_git_clients_on_windows_and_os_x -- View this message in context: http://git.661346.n2.nabble.com/Upgrade-Git-in-openSUSE13-1-tp7623397p7623406.html Sent from

Re: Upgrade Git in openSUSE13.1

2014-12-24 Thread Yue Lin Ho
go https://msysgit.github.io/ -- View this message in context: http://git.661346.n2.nabble.com/Upgrade-Git-in-openSUSE13-1-tp7623397p7623405.html Sent from the git mailing list archive at Nabble.com. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to m

Re: [PATCH v4 0/1] Use absolute paths of lockfiles

2014-10-14 Thread Yue Lin Ho
Hi Michael: Good Morning. :) I see mh/lockfile and mh/lockfile-stdio were ​graduated to "master". So. does this patch continue? On top of mh/lockfile-stdio? Thank you. ^_^ Yue Lin Ho -- View this message in context: http://git.661346.n2.nabble.com/What-s-cooking-in-git-git-Aug-2

Re: [PATCH v4 0/1] Use absolute paths of lockfiles

2014-09-09 Thread Yue Lin Ho
Hi Duy, Michael, Junio C Hamano: Thanks for working on lock file issue. Thank you! Thank you~ ^_^ Yue Lin Ho -- View this message in context: http://git.661346.n2.nabble.com/What-s-cooking-in-git-git-Aug-2014-02-Fri-8-tp7616651p7618314.html Sent from the git mailing list archive at

Re: [PATCH v3 1/3] lockfile.c: remove PATH_MAX limitation (except in resolve_symlink)

2014-09-03 Thread Yue Lin Ho
k on errors . lockfile: unlock file if lockfile permissions cannot be adjusted . rollback_lock_file(): set fd to -1 . rollback_lock_file(): do not clear filename redundantly . api-lockfile: expand the documentation . unable_to_lock_die(): rename function from unable_to_lock_index_die() Expecti

Re: What's cooking in git.git (Aug 2014, #04; Tue, 26)

2014-08-27 Thread Yue Lin Ho
nd/lock-paths-absolute (2014-08-01) 3 commits > . lockfile.c: store absolute path > . lockfile.c: remove PATH_MAX limit in resolve_symlink() > . lockfile.c: remove PATH_MAX limitation (except in resolve_symlink) > > Will drop and ask ​​Michael to possibly cooperate and merge with &

Re: [PATCH v2 2/2] Make locked paths absolute when current directory is changed

2014-07-30 Thread Yue Lin Ho
-2014-04-Tue-22-td7615627.html seems no related information there. So, could you please tell me how to trace it? Thank you. ^_^ Yue Lin Ho ​ -- View this message in context: http://git.661346.n2.nabble.com/PATCH-Make-locked-paths-absolute-when-current-directory-is-changed-tp7615398p7616119.html Se

Re: git update-index not delete lock file when using different worktree

2014-07-18 Thread Yue Lin Ho
\sequencer.c Yue Lin -- View this message in context: http://git.661346.n2.nabble.com/git-update-index-not-delete-lock-file-when-using-different-worktree-tp7615300p7615378.html Sent from the git mailing list archive at Nabble.com. -- To unsubscribe from this list: send the line "unsubscribe gi

Re: git update-index not delete lock file when using different worktree

2014-07-17 Thread Yue Lin Ho
I see that refresh() of update_index.c calls setup_work_tree() to change dir to working tree. And the dir is not changed back to git dir before commit_lock_file() or rollback_lock_file() is called. So, commit_lock_file() rename file failed. or rollback_lock_file() delete file failed. -- View th

git update-index not delete lock file when using different worktree

2014-07-16 Thread Yue Lin Ho
This is a [issue from TortoiseGit](https://code.google.com/p/tortoisegit/issues/detail?id=2233). After doing some test, I report it here. The following is the testing information I have tested. ### Folder Structure ``` Test |-- myrepo | |-- bar.txt | |-- foo.txt | |-- myrepo.git

Re: The different EOL behavior between libgit2-based software and official Git

2014-06-20 Thread Yue Lin Ho
Wow! P.S. A note: libgit2 just has a PR that try to be identical with official git 2.0.0. See https://github.com/libgit2/libgit2/pull/2432 -- View this message in context: http://git.661346.n2.nabble.com/The-different-EOL-behavior-between-libgit2-based-software-and-official-Git-tp7613670p76138

Re: The different EOL behavior between libgit2-based software and official Git

2014-06-19 Thread Yue Lin Ho
Hi Torsten Bögershausen: Since you mail to msysGit first, I reply there. (https://groups.google.com/forum/#!topic/msysgit/EDD3RipNeBQ) Thank you again. ^_^ Yue Lin Ho -- View this message in context: http://git.661346.n2.nabble.com/The-different-EOL-behavior-between-libgit2-based-software

The different EOL behavior between libgit2-based software and official Git

2014-06-18 Thread Yue Lin Ho
, you might take a look at my testing repository on GitHub. (https://github.com/YueLinHo/TestAutoCrlf) Thank you. Yue Lin Ho -- View this message in context: http://git.661346.n2.nabble.com/The-different-EOL-behavior-between-libgit2-based-software-and-official-Git-tp7613670.html Sent from the