git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 3/5] setup_revisions: remember whether a ref was positive or not

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
Aug 8, 2011, 23:04 UTC
Message-ID
<CAGdFq_gY3-1fv8TiHj=8ppS=AE4B-rwwUL-iKHcjvVtqQa8UAA@mail.gmail.com>
In-Reply-To
<7vd3gfv7gd.fsf@alter.siamese.dyndns.org>
Heya,
On Tue, Aug 9, 2011 at 00:56, Junio C Hamano <gitster@pobox.com> wrote:
> Would we have the same issue with "git bundle", by the way, caused by the
> same setup_revisions() limitation?  Over there we would also need to
> decide the set of refs that the user wanted to record their values while
> computing the set of commits we would need to transfer.
I think so.
$ git init test && cd test
Initialized empty Git repository in /home/sverre/code/test/test/.git/
$ echo content >> file
$ git add file && git commit -m "first"
[master (root-commit) c7f5a27] first
 1 files changed, 1 insertions(+), 0 deletions(-)
 create mode 100644 file
$ (git init ../another && cd ../another && git pull ../test)
Initialized empty Git repository in /home/sverre/code/another/.git/
remote: Counting objects: 3, done.
remote: Total 3 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (3/3), done.
From ../test
 * branch            HEAD       -> FETCH_HEAD
sverre@laptop-sverre:~/code/test
$ git branch second
$ git bundle create bundle second
Counting objects: 3, done.
Writing objects: 100% (3/3), 215 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
sverre@laptop-sverre:~/code/test
$ mv bundle ../another/
$ (cd ../another/ && git bundle unbundle bundle)
c7f5a273b11a438bf78aecff0dfcbb8b16344555 refs/heads/second
$ (cd ../another/ && git for-each-ref)
c7f5a273b11a438bf78aecff0dfcbb8b16344555 commit	refs/heads/master
-- 
Cheers,

Sverre Rabbelier
Previous: Junio C HamanoNext: Johannes Schindelin
Message 24 of 29 in “fast-export: prepare for remote helpers awesomeness”
  1. 0/5 fast-export: prepare for remote helpers awesomenessSverre Rabbelier, Jul 24, 2011
  2. 1/5 t9350: point out that refs are not updated correctlySverre Rabbelier, Jul 24, 2011
  3. 2/5 fast-export: do not refer to non-existing marksSverre Rabbelier, Jul 24, 2011
  4. 3/5 setup_revisions: remember whether a ref was positive or notSverre Rabbelier, Jul 24, 2011
  5. Junio C HamanoJul 24, 2011
  6. Junio C HamanoJul 24, 2011
  7. Sverre RabbelierAug 3, 2011
  8. Junio C HamanoAug 3, 2011
  9. Johannes SchindelinAug 8, 2011
  10. Junio C HamanoAug 8, 2011
  11. Sverre RabbelierAug 8, 2011
  12. Junio C HamanoAug 8, 2011
  13. Sverre RabbelierAug 8, 2011
  14. Junio C HamanoAug 8, 2011
  15. Sverre RabbelierAug 8, 2011
  16. Junio C HamanoAug 8, 2011
  17. Sverre RabbelierAug 8, 2011
  18. Junio C HamanoAug 8, 2011
  19. Sverre RabbelierAug 8, 2011
  20. Junio C HamanoAug 8, 2011
  21. Junio C HamanoAug 8, 2011
  22. Sverre RabbelierAug 8, 2011
  23. Junio C HamanoAug 8, 2011
  24. Sverre RabbelierAug 8, 2011
  25. Johannes SchindelinJul 26, 2011
  26. 4/5 fast-export: do not export negative refsSverre Rabbelier, Jul 24, 2011
  27. Junio C HamanoJul 24, 2011
  28. Johannes SchindelinJul 26, 2011
  29. 5/5 setup_revisions: remember whether a ref was positive or notSverre Rabbelier, Jul 24, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.