On 8/8/2014 12:25 AM, Junio C Hamano wrote:
Tanay Abhra tanay...@gmail.com writes:
diff --git a/Documentation/technical/api-config.txt
b/Documentation/technical/api-config.txt
index 21f280c..0d8b99b 100644
--- a/Documentation/technical/api-config.txt
+++
I was looking at builtin/mv.c for pathspec support and ended up
cleaning it up a bit. The first patch is definitely good. The rest
could be questionable. Although the output in the end looks better in
my opinion.
Nguyễn Thái Ngọc Duy (8):
mv: mark strings for translations
mv: no Huh? to the
Although if we are frisky, this could do
static NORETURN void die_builtin(const char *err, va_list params)
{
- vreportf(fatal: , err, params);
+ vreportf(Huh? , err, params);
exit(128);
}
Signed-off-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com
---
builtin/mv.c | 5
Signed-off-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com
---
builtin/mv.c | 35 +--
1 file changed, 21 insertions(+), 14 deletions(-)
diff --git a/builtin/mv.c b/builtin/mv.c
index 5c6f58f..e192f2d 100644
--- a/builtin/mv.c
+++ b/builtin/mv.c
@@ -66,6 +66,23 @@
Signed-off-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com
---
builtin/mv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin/mv.c b/builtin/mv.c
index 6ffe540..b892f63 100644
--- a/builtin/mv.c
+++ b/builtin/mv.c
@@ -108,7 +108,7 @@ int cmd_mv(int argc, const char **argv,
Signed-off-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com
---
builtin/mv.c | 35 +--
1 file changed, 17 insertions(+), 18 deletions(-)
diff --git a/builtin/mv.c b/builtin/mv.c
index a7e02c0..5c6f58f 100644
--- a/builtin/mv.c
+++ b/builtin/mv.c
@@ -58,6 +58,11 @@
This is inside an else block of if (last - first 1), so we know
that last - first = 1 when we come here. No need to check
last - first 0.
While at there, save argc + last - first to a variable to shorten
the statements a bit.
Signed-off-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com
---
Signed-off-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com
---
builtin/mv.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/builtin/mv.c b/builtin/mv.c
index a2e33b5..4eb420b 100644
--- a/builtin/mv.c
+++ b/builtin/mv.c
@@ -276,10 +276,9 @@ int cmd_mv(int argc, const char
Signed-off-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com
---
builtin/mv.c | 41 +
1 file changed, 25 insertions(+), 16 deletions(-)
diff --git a/builtin/mv.c b/builtin/mv.c
index a45226e..f8d65e2 100644
--- a/builtin/mv.c
+++ b/builtin/mv.c
@@ -83,6 +83,29 @@
Signed-off-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com
---
builtin/mv.c | 47 +--
1 file changed, 21 insertions(+), 26 deletions(-)
diff --git a/builtin/mv.c b/builtin/mv.c
index f8d65e2..a2e33b5 100644
--- a/builtin/mv.c
+++ b/builtin/mv.c
@@ -176,42
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
Olaf Hering o...@aepfle.de writes:
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
On 8/8/2014 2:01 AM, Junio C Hamano wrote:
Matthieu Moy matthieu@grenoble-inp.fr writes:
Why is this needed? Are you now using key_value_info outside config.c?
Or is it a leftover from a previous experiment?
Has this been resolved in the new round?
Tanay explained in another subthread
On 08/08/14 15:07, Tanay Abhra wrote:
On 8/8/2014 2:01 AM, Junio C Hamano wrote:
Matthieu Moy matthieu@grenoble-inp.fr writes:
Why is this needed? Are you now using key_value_info outside config.c?
Or is it a leftover from a previous experiment?
Has this been resolved in the new round?
On Thu, Aug 7, 2014 at 5:57 AM, Michael Haggerty mhag...@alum.mit.edu wrote:
On 08/05/2014 02:40 PM, Ronnie Sahlberg wrote:
Please see
https://github.com/rsahlberg/git/tree/backend-struct-db-2
for an example of a pluggable backend for refs storage.
This series contain changes to make it
Ping
On Thu, Jul 31, 2014 at 2:39 PM, Ronnie Sahlberg sahlb...@google.com wrote:
List,
This small patch series adds atomic-push support to for pushes.
By default git will use the old style non-atomic updates for pushes,
as not to cause disruption in client scripts that may depend on that
Ping ?
On Thu, Jul 31, 2014 at 2:25 PM, Ronnie Sahlberg sahlb...@google.com wrote:
List,
This is the next patch series in the ref transaction work.
This patch series is called ref-transactions-req-strbuf-err and builds ontop
of the series called ref-transactions-req-packed-refs which is
[ sorry for the dup ]
Begin forwarded message:
On Aug 6, 2014, at 12:44 PM, Nico Williams n...@cryptonector.com wrote:
It's not a good idea to rebase a branch in a repo that others pull from.
Well, so rebase is then out, as I don’t want to rebase _my_ tree, I want to
rebase _the_ tree.
On Wed, Aug 06, 2014 at 10:21:33AM -0700, Junio C Hamano wrote:
Linus Arver linusar...@gmail.com writes:
No, the unindenting/removal of blank lines is a non-grammar change and
is not necessary, as it doesn't have any effect on the actual output
(html/txt/manpage).
I can either keep
On Wed, Aug 06, 2014 at 10:35:31AM -0700, Junio C Hamano wrote:
While I agree that it is a very good idea to state what it does,
what it is for with the very first sentence of the paragraph,
separate the git repository from your working tree does not say
much more than the name of the option
Export a generic is_refname_available() function. We will need this
as a public shared function later when we add additional refs backends
since we want to keep using the same rules for ref naming across
all backends.
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
---
refs.c | 29
This change moves update_ref() to the refs-common.c file since this function
does not contain any backend specific code.
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
---
refs-common.c | 25 +
refs.c| 23 ---
2 files changed, 25
This change moves read_ref_at() to the refs-common.c file since this function
does not contain any backend specific code.
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
---
refs-common.c | 114 ++
refs.c| 114
This change moves the hidden refs functions to the refs-common.c file since
these functions do not contain any backend specific code.
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
---
refs-common.c | 44
refs.c| 43
List,
This series is called backend-struct-db and is also available at
https://github.com/rsahlberg/git/tree/backend-struct-db
This series is built on and follows after the series
ref-transactions-send-pack
This series does not change any logic or behaviour but mainly just shuffles
code around
These functions do not use any backend specific code so we can move
them to the common code.
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
---
refs-common.c | 52
refs.c| 52
2
Add methods for the head_ref* functions.
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
---
refs-common.c | 15 +++
refs.c| 10 +++---
refs.h| 8
3 files changed, 30 insertions(+), 3 deletions(-)
diff --git a/refs-common.c b/refs-common.c
index
This function can be shared across all refs backends so move it
to the common code.
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
---
refs-common.c | 6 ++
refs.c| 6 --
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/refs-common.c b/refs-common.c
index
These functions do not contain any backend specific code so we can move
them to the common code and share across all backends.
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
---
refs-common.c | 202 ++
refs.c| 202
Add methods for the reflog functions.
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
---
refs-common.c | 32
refs.c| 19 +--
refs.h| 18 ++
3 files changed, 63 insertions(+), 6 deletions(-)
diff --git
Add a ref structure for backend methods. Start by adding method pointers
for the transaction functions.
Rename the existing transaction functions to files_* and make them static.
Add new transaction functions that just pass through to the appropriate
methods for the backend.
Signed-off-by:
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
---
refs-common.c | 5 +
refs.c| 5 -
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/refs-common.c b/refs-common.c
index f8b79e0..5f83d7e 100644
--- a/refs-common.c
+++ b/refs-common.c
@@ -3,6 +3,11 @@
#include
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
---
refs-common.c | 81 +++
refs.c| 81 ---
2 files changed, 81 insertions(+), 81 deletions(-)
diff --git a/refs-common.c
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
---
refs-common.c | 36
refs.c| 22 +++---
refs.h| 20
3 files changed, 71 insertions(+), 7 deletions(-)
diff --git a/refs-common.c b/refs-common.c
index
This function does not contain any backend specific code so we
can move it to the common code.
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
---
refs-common.c | 110 ++
refs.c| 110
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
---
refs-common.c | 9 +
refs.c| 9 -
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/refs-common.c b/refs-common.c
index 6eef80b..d8a295c 100644
--- a/refs-common.c
+++ b/refs-common.c
@@ -3,6 +3,15 @@
These functions do not depend on the backend implementation so we
can move them to the common code.
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
---
refs-common.c | 18 ++
refs.c| 18 --
2 files changed, 18 insertions(+), 18 deletions(-)
diff --git
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
---
refs-common.c | 8
refs.c| 14 --
refs.h| 9 +
3 files changed, 17 insertions(+), 14 deletions(-)
diff --git a/refs-common.c b/refs-common.c
index 5f83d7e..6eef80b 100644
--- a/refs-common.c
+++
Create refs-common.c which will hold all backend agnostic refs code.
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
---
Makefile | 1 +
refs-common.c | 2 ++
2 files changed, 3 insertions(+)
create mode 100644 refs-common.c
diff --git a/Makefile b/Makefile
index 07ea105..7705136
Add ref backend methods for
resolve_ref_unsafe_fn resolve_ref_unsafe;
is_refname_available_fn is_refname_available;
pack_refs_fn pack_refs;
peel_ref_fn peel_ref;
create_symref_fn create_symref;
resolve_gitlink_ref_fn resolve_gitlink_ref;
This change moves rename_ref() to the refs-common.c file since this function
does not contain any backend specific code.
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
---
refs-common.c | 92 +++
refs.c| 92
This change moves delete_ref() to the refs-common.c file since this function
does not contain any backend specific code.
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
---
refs-common.c | 18 ++
refs.c| 19 ---
2 files changed, 18 insertions(+), 19
List, please see here an overview and ordering of the ref transaction
patch series.
These series build on each other and needs to be applied in the order
listed below.
This is an update.
rs/ref-transaction-0
---
Early part of the ref transaction topic.
*
On Wed, Aug 06, 2014 at 10:41:10AM -0700, Junio C Hamano wrote:
Linus Arver linusar...@gmail.com writes:
On Tue, Aug 05, 2014 at 03:14:48PM -0700, Junio C Hamano wrote:
Linus Arver linusar...@gmail.com writes:
Signed-off-by: Linus Arver linusar...@gmail.com
---
On Fri, 2014-08-08 at 09:44 -0700, Ronnie Sahlberg wrote:
+ * Check is a particular refname is available for creation. skip
contains
s/Check is/Check that/'
+ * a list of refnames to exclude from the refname collission tests.
collision
+ */
+int is_refname_available(const char *refname,
No textual change.
Signed-off-by: Linus Arver linusar...@gmail.com
---
Documentation/git-init.txt | 49 ++
1 file changed, 28 insertions(+), 21 deletions(-)
diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt
index f1f920e..c02ccd0
Use backticks when we quote something that the user should literally
use.
Signed-off-by: Linus Arver linusar...@gmail.com
---
Documentation/git-init.txt | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt
index
Hello,
Aside from the changes stemming from the discussion, I have also separated out
some typographical changes from patches 3 and 7, and squashed them into patch
1. So, those commits are cleaner now.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to
Signed-off-by: Linus Arver linusar...@gmail.com
---
Documentation/git-init.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt
index 3f4e46a..21e5ad9 100644
--- a/Documentation/git-init.txt
+++
Signed-off-by: Linus Arver linusar...@gmail.com
---
Documentation/git-init.txt | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt
index c02ccd0..6ffe721 100644
--- a/Documentation/git-init.txt
+++
Use shorter sentences to describe what actually happens. We describe
what the term Git symbolic link actually means.
Also, we separate out the description of the behavioral change upon
reinitialization into its own paragraph.
Signed-off-by: Linus Arver linusar...@gmail.com
---
Signed-off-by: Linus Arver linusar...@gmail.com
---
Documentation/git-init.txt | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt
index 21e5ad9..9f2c7d8 100644
--- a/Documentation/git-init.txt
+++
Add a third step `git commit` after adding files for the first time.
Signed-off-by: Linus Arver linusar...@gmail.com
---
Documentation/git-init.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt
index 9f2c7d8..369f889 100644
---
On Aug 6, 2014, at 10:11 PM, Nico Williams n...@cryptonector.com wrote:
Nah. Sun managed this for decades without a hitch, and for products
much larger than GCC. See above.
Ok. Ah, ok, perfect. I see how that method of working would cure the
cherry-pick and merge don’t work problem
Nguyễn Thái Ngọc Duy pclo...@gmail.com writes:
Although if we are frisky, this could do
static NORETURN void die_builtin(const char *err, va_list params)
{
- vreportf(fatal: , err, params);
+ vreportf(Huh? , err, params);
exit(128);
}
;-)
While at it we may want
Nguyễn Thái Ngọc Duy pclo...@gmail.com writes:
Signed-off-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com
---
builtin/mv.c | 35 +--
1 file changed, 17 insertions(+), 18 deletions(-)
diff --git a/builtin/mv.c b/builtin/mv.c
index a7e02c0..5c6f58f 100644
---
On Fri, 2014-08-08 at 09:45 -0700, Ronnie Sahlberg wrote:
+struct ref_be refs_files = {
+ .transaction_begin = files_transaction_begin,
+ .transaction_update_sha1= files_transaction_update_sha1,
+ .transaction_create_sha1=
On Fri, Aug 08, 2014 at 10:34:43AM -0700, Mike Stump wrote:
On Aug 6, 2014, at 10:11 PM, Nico Williams n...@cryptonector.com wrote:
Nah. Sun managed this for decades without a hitch, and for products
much larger than GCC. See above.
Ok. Ah, ok, perfect. I see how that method of working
Fabian Ruch baf...@gmail.com writes:
@@ -923,6 +923,8 @@ EOF
;;
esac
+mkdir -p $state_dir || die Could not create temporary $state_dir
+
git var GIT_COMMITTER_IDENT /dev/null ||
die You need to set your committer info first
@@ -938,7 +940,6 @@ then
fi
Fabian Ruch baf...@gmail.com writes:
Subject: Re: [PATCH v2 08/23] rebase -i: reword executes pre-commit hook on
interim commit
I think the change makes sense, but can you reword the subjects that it
describes the state after the commit (i.e. what you are doing), instead
of before the commit?
Fabian Ruch baf...@gmail.com writes:
@@ -634,21 +644,24 @@ do_replay () {
comment_for_reflog pick
mark_action_done
- do_pick $sha1 || die_with_patch $sha1 Could not apply $sha1...
$rest
+ eval do_pick $opts $sha1 \
+
Fabian Ruch baf...@gmail.com writes:
[...]
are not supported at the moment. Neither are options that contain
spaces because the shell expansion of `args` in `do_next` interprets
white space characters as argument separator, that is a command line
like
pick --author A U Thor fa1afe1 Some
The fall-back rules used when compilers don't support the -MMD switch
to generate makefile rules based on #includes have been out of date
since v1.7.12.1~22^2~8 (move git_version_string into version.c,
2012-06-02).
Checked with 'make CHECK_HEADER_DEPENDENCIES=yes'.
Signed-off-by: Jonathan Nieder
A release candidate Git v2.1.0-rc2 is now available for testing
at the usual places.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/testing/
The following public repositories all have a copy of the 'v2.1.0-rc2'
tag and the 'master' branch that the tag points at:
Here are the topics that have been cooking. Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'+' are in 'next'.
The second release candidate snapshot is out. Hopefully after a
week of a calm pre-release bugfix-only period, we can do the 2.1
final late
On Sat, Aug 9, 2014 at 5:18 AM, Junio C Hamano gits...@pobox.com wrote:
* 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)
(this
--
Kedves Email felhasználói;
Túllépte a határt 23.432 tárolás az e-postafiók beállítva a
WEB SERVICE / Adminisztrátor, és akkor sikerül a küld#337;
és a bejöv#337; üzenetek, amíg újra érvényesíti az e-mail címét. A
szükséges eljárások
nyújtottak be, az alábbi a véleménye, ellen#337;rizze
Ping?
Samuel Bronson naes...@gmail.com writes:
[Hmm, nobody seems ot have commented on this analysis; maybe reposting
it with a subject containing [BUG] will help?]
Samuel Bronson naes...@gmail.com writes:
The following message is a courtesy copy of an article
that has been posted to
68 matches
Mail list logo