{"thread":{"id":"2058","subject":"openbsd version?","startedAt":"2005-10-10T16:12:34Z","lastAt":"2005-10-13T08:29:28Z","messageCount":17,"participants":["Randal L. Schwartz","Peter Eriksen","Linus Torvalds","Junio C Hamano","Johannes Schindelin","Sven Verdoolaege","H. Peter Anvin","Daniel Barkalow"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"9887","messageId":"8664s5gxl9.fsf@blue.stonehenge.com","threadId":"2058","inReplyTo":null,"subject":"openbsd version?","fromName":"Randal L. Schwartz","fromEmail":"merlyn@stonehenge.com","sentAt":"2005-10-10T16:12:34Z","receivedAt":"2005-10-10T16:12:34Z","isPatch":false,"sender":{"key":"merlyn@stonehenge.com","avatar":"https://gravatar.com/avatar/dc528d210743ff0333e6213f9ee7b33b23f1b7bc1f3c5a8c2d819074ecd7ab19?d=mp&s=160"},"body":"\nI noticed \"openbsd\" in the operating systems detected in Makefile,\nbut when I tried this on my openbsd system, I get an abort here:\n\n gcc -g -O2 -Wall -I/usr/local/include -L/usr/local/lib '-DSHA1_HEADER=' -o git-mailinfo mailinfo.o libgit.a -liconv\n mailinfo.o(.text+0x22d): In function `slurp_attr':\n /opt/git/src/git-snapshot-20051010/mailinfo.c:130: undefined reference to `strcasestr'\n mailinfo.o(.text+0x2a9): In function `handle_subcontent_type':\n /opt/git/src/git-snapshot-20051010/mailinfo.c:155: undefined reference to `strcasestr'\n mailinfo.o(.text+0x39d): In function `handle_content_transfer_encoding':\n /opt/git/src/git-snapshot-20051010/mailinfo.c:181: undefined reference to `strcasestr'\n mailinfo.o(.text+0x3c6):/opt/git/src/git-snapshot-20051010/mailinfo.c:183: undefined reference to `strcasestr'\n collect2: ld returned 1 exit status\n gmake: *** [git-mailinfo] Error 1\n\nWhat am I doing wrong?\n\n-- \nRandal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095\n \nPerl/Unix/security consulting, Technical writing, Comedy, etc. etc.\nSee PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!\n"},{"id":"9888","messageId":"20051010162908.GA23401@ebar091.ebar.dtu.dk","threadId":"2058","inReplyTo":"8664s5gxl9.fsf@blue.stonehenge.com","subject":"Re: openbsd version?","fromName":"Peter Eriksen","fromEmail":"s022018@student.dtu.dk","sentAt":"2005-10-10T16:29:08Z","receivedAt":"2005-10-10T16:29:08Z","isPatch":false,"sender":{"key":"s022018@student.dtu.dk","avatar":null},"body":"On Mon, Oct 10, 2005 at 09:12:34AM -0700, Randal L. Schwartz wrote:\n> \n> I noticed \"openbsd\" in the operating systems detected in Makefile,\n> but when I tried this on my openbsd system, I get an abort here:\n> \n> gcc -g -O2 -Wall -I/usr/local/include -L/usr/local/lib '-DSHA1_HEADER=' -o git-mailinfo mailinfo.o libgit.a -liconv\n> mailinfo.o(.text+0x22d): In function `slurp_attr':\n> /opt/git/src/git-snapshot-20051010/mailinfo.c:130: undefined reference to `strcasestr'\n> mailinfo.o(.text+0x2a9): In function `handle_subcontent_type':\n> /opt/git/src/git-snapshot-20051010/mailinfo.c:155: undefined reference to `strcasestr'\n> mailinfo.o(.text+0x39d): In function `handle_content_transfer_encoding':\n> /opt/git/src/git-snapshot-20051010/mailinfo.c:181: undefined reference to `strcasestr'\n> mailinfo.o(.text+0x3c6):/opt/git/src/git-snapshot-20051010/mailinfo.c:183: undefined reference to `strcasestr'\n> collect2: ld returned 1 exit status\n> gmake: *** [git-mailinfo] Error 1\n> \n> What am I doing wrong?\n\nYou need to compile with\n\n$ gmake NO_STRCASESTR=Indeed\n\nPeter\n"},{"id":"9889","messageId":"Pine.LNX.4.64.0510100939320.14597@g5.osdl.org","threadId":"2058","inReplyTo":"8664s5gxl9.fsf@blue.stonehenge.com","subject":"Re: openbsd version?","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2005-10-10T16:41:05Z","receivedAt":"2005-10-10T16:41:05Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Mon, 10 Oct 2005, Randal L. Schwartz wrote:\n> \n> I noticed \"openbsd\" in the operating systems detected in Makefile,\n> but when I tried this on my openbsd system, I get an abort here:\n> \n> /opt/git/src/git-snapshot-20051010/mailinfo.c:130: undefined reference to `strcasestr'\n\nEither do\n\n\tmake NO_STRCASESTR=1 ..\n\nor add that explicitly to the makefile in the OpenBSD rules and send Junio \na tested patch ;)\n\n\t\tLinus\n"},{"id":"9906","messageId":"7vvf0542fs.fsf@assigned-by-dhcp.cox.net","threadId":"2058","inReplyTo":"Pine.LNX.4.64.0510100939320.14597@g5.osdl.org","subject":"Re: openbsd version?","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-10-10T19:06:15Z","receivedAt":"2005-10-10T19:06:15Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Linus Torvalds writes:\n\n> Either do\n>\n> \tmake NO_STRCASESTR=1 ..\n>\n> or add that explicitly to the makefile in the OpenBSD rules and send Junio \n> a tested patch ;)\n\nThanks; this has been resolved underwater.\n"},{"id":"9908","messageId":"864q7pdvcn.fsf@blue.stonehenge.com","threadId":"2058","inReplyTo":"7vvf0542fs.fsf@assigned-by-dhcp.cox.net","subject":"Re: openbsd version?","fromName":"Randal L. Schwartz","fromEmail":"merlyn@stonehenge.com","sentAt":"2005-10-10T19:29:12Z","receivedAt":"2005-10-10T19:29:12Z","isPatch":false,"sender":{"key":"merlyn@stonehenge.com","avatar":"https://gravatar.com/avatar/dc528d210743ff0333e6213f9ee7b33b23f1b7bc1f3c5a8c2d819074ecd7ab19?d=mp&s=160"},"body":">>>>> \"Junio\" == Junio C Hamano writes:\n\nJunio> Linus Torvalds writes:\n>> Either do\n>> \n>> make NO_STRCASESTR=1 ..\n>> \n>> or add that explicitly to the makefile in the OpenBSD rules and send Junio \n>> a tested patch ;)\n\nJunio> Thanks; this has been resolved underwater.\n\nAnd yes, I made my first patch with git today! But I cut-n-pasted\nit and blew the leading tabs.\n\nRelated question. I created \"mybranch\" to do the patch, but how\ncan I have my repository now forget that mybranch was ever made?\nIs it sufficient to remove the branch link, and then type some \"fsck\"\noperation?\n\nThat's also a question in general... how can I remove a commit,\nknowing that I'd never refer to it again? Or is disk space so cheap\nthat it wouldn't make any difference anyway?\n\n-- \nRandal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095\n \nPerl/Unix/security consulting, Technical writing, Comedy, etc. etc.\nSee PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!\n"},{"id":"9915","messageId":"7vll113yjs.fsf@assigned-by-dhcp.cox.net","threadId":"2058","inReplyTo":"864q7pdvcn.fsf@blue.stonehenge.com","subject":"Re: openbsd version?","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-10-10T20:30:15Z","receivedAt":"2005-10-10T20:30:15Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"merlyn@stonehenge.com (Randal L. Schwartz) writes:\n\n> Related question. I created \"mybranch\" to do the patch, but how\n> can I have my repository now forget that mybranch was ever made?\n> Is it sufficient to remove the branch link, and then type some \"fsck\"\n> operation?\n\nRemoving non-current branch -- you may need to do -D instead of -d. \n\n$ git branch -d mybranch\n\n> That's also a question in general... how can I remove a commit,\n> knowing that I'd never refer to it again? Or is disk space so cheap\n> that it wouldn't make any difference anyway?\n\nRemoving from the tip of the current branch:\n\n$ git reset HEAD^\n\nRemoving from the tip of non-current branch:\n\n$ git update-ref mybranch mybranch^\n"},{"id":"9917","messageId":"86ek6tcdou.fsf@blue.stonehenge.com","threadId":"2058","inReplyTo":"7vll113yjs.fsf@assigned-by-dhcp.cox.net","subject":"Re: openbsd version?","fromName":"Randal L. Schwartz","fromEmail":"merlyn@stonehenge.com","sentAt":"2005-10-10T20:36:01Z","receivedAt":"2005-10-10T20:36:01Z","isPatch":false,"sender":{"key":"merlyn@stonehenge.com","avatar":"https://gravatar.com/avatar/dc528d210743ff0333e6213f9ee7b33b23f1b7bc1f3c5a8c2d819074ecd7ab19?d=mp&s=160"},"body":">>>>> \"Junio\" == Junio C Hamano writes:\n\nJunio> Removing non-current branch -- you may need to do -D instead of -d. \n\nJunio> $ git branch -d mybranch\n\nUndocumented secret switches. Nice. No wonder\nI couldn't find it.\n\n>> That's also a question in general... how can I remove a commit,\n>> knowing that I'd never refer to it again? Or is disk space so cheap\n>> that it wouldn't make any difference anyway?\n\nJunio> Removing from the tip of the current branch:\n\nJunio> $ git reset HEAD^\n\nJunio> Removing from the tip of non-current branch:\n\nJunio> $ git update-ref mybranch mybranch^\n\nDo these also flush any related object files? Or do I need git-fsck still?\n\n-- \nRandal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095\n \nPerl/Unix/security consulting, Technical writing, Comedy, etc. etc.\nSee PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!\n"},{"id":"9921","messageId":"Pine.LNX.4.63.0510102248570.10402@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"2058","inReplyTo":"86ek6tcdou.fsf@blue.stonehenge.com","subject":"Re: openbsd version?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2005-10-10T20:49:37Z","receivedAt":"2005-10-10T20:49:37Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Mon, 10 Oct 2005, Randal L. Schwartz wrote:\n\n> >>>>> \"Junio\" == Junio C Hamano writes:\n> \n> Junio> Removing non-current branch -- you may need to do -D instead of -d. \n> \n> Junio> $ git branch -d mybranch\n> \n> Undocumented secret switches. Nice. No wonder\n> I couldn't find it.\n\nMaybe he who found the documentation lacking is going to fix \nit?\n"},{"id":"9920","messageId":"86y851aydl.fsf@blue.stonehenge.com","threadId":"2058","inReplyTo":"Pine.LNX.4.63.0510102248570.10402@wbgn013.biozentrum.uni-wuerzburg.de","subject":"Re: openbsd version?","fromName":"Randal L. Schwartz","fromEmail":"merlyn@stonehenge.com","sentAt":"2005-10-10T20:52:06Z","receivedAt":"2005-10-10T20:52:06Z","isPatch":false,"sender":{"key":"merlyn@stonehenge.com","avatar":"https://gravatar.com/avatar/dc528d210743ff0333e6213f9ee7b33b23f1b7bc1f3c5a8c2d819074ecd7ab19?d=mp&s=160"},"body":">>>>> \"Johannes\" == Johannes Schindelin writes:\n\n>> Undocumented secret switches. Nice. No wonder\n>> I couldn't find it.\n\nJohannes> Maybe he who found the documentation lacking is going to fix \nJohannes> it?\n\nI'd be happy to do that. But as a tech writer, I know that it's\ninsane to not work at least from an implementor's rough draft, to at\nleast understand the intent of a mechanism, if not the precise design.\nThere's no implementor's rough draft here, so I can't help.\n\n-- \nRandal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095\n \nPerl/Unix/security consulting, Technical writing, Comedy, etc. etc.\nSee PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!\n"},{"id":"9928","messageId":"20051010210007.GJ8383MdfPADPa@greensroom.kotnet.org","threadId":"2058","inReplyTo":"7vll113yjs.fsf@assigned-by-dhcp.cox.net","subject":"Re: openbsd version?","fromName":"Sven Verdoolaege","fromEmail":"skimo@kotnet.org","sentAt":"2005-10-10T21:00:08Z","receivedAt":"2005-10-10T21:00:08Z","isPatch":false,"sender":{"key":"skimo@kotnet.org","avatar":null},"body":"On Mon, Oct 10, 2005 at 01:30:15PM -0700, Junio C Hamano wrote:\n> Removing from the tip of non-current branch:\n> \n> $ git update-ref mybranch mybranch^\n> \n\nI think you mean \n\n$ git-update-ref refs/heads/mybranch mybranch^\n\nWhich reminds me... try this:\n\nbash-3.00$ git-init-db \ndefaulting to local storage area\nbash-3.00$ touch a\nbash-3.00$ git-update-index --add a\nbash-3.00$ git commit -m 'a'\nCommitting initial tree 496d6428b9cf92981dc9495211e6e1120fb6f2ba\nbash-3.00$ touch b\nbash-3.00$ git-update-index --add b\nbash-3.00$ git commit -m 'b'\nbash-3.00$ git checkout -b branch\nbash-3.00$ git-update-ref master master^\nbash-3.00$ git checkout master\nbash-3.00$ git-status\n#\n# Updated but not checked in:\n# (will commit)\n#\n# deleted: b\n#\n\n(Hint: there are now two masters)\n\nskimo\n"},{"id":"9929","messageId":"434AD742.2090109@zytor.com","threadId":"2058","inReplyTo":"86y851aydl.fsf@blue.stonehenge.com","subject":"Re: openbsd version?","fromName":"H. Peter Anvin","fromEmail":"hpa@zytor.com","sentAt":"2005-10-10T21:04:02Z","receivedAt":"2005-10-10T21:04:02Z","isPatch":false,"sender":{"key":"hpa@zytor.com","avatar":null},"body":"Randal L. Schwartz wrote:\n> \n> Johannes> Maybe he who found the documentation lacking is going to fix \n> Johannes> it?\n> \n> I'd be happy to do that. But as a tech writer, I know that it's\n> insane to not work at least from an implementor's rough draft, to at\n> least understand the intent of a mechanism, if not the precise design.\n> There's no implementor's rough draft here, so I can't help.\n> \n\nSounds like an offer to send Mr. Schwartz some notes to work from. In \nmy experience, sending notes to a good tech writer is about an order of \nmagnitude less painful than writing polished documentation, so that \nshould be easier.\n\n\t-hpa\n"},{"id":"9930","messageId":"86ll11axqj.fsf@blue.stonehenge.com","threadId":"2058","inReplyTo":"434AD742.2090109@zytor.com","subject":"Re: openbsd version?","fromName":"Randal L. Schwartz","fromEmail":"merlyn@stonehenge.com","sentAt":"2005-10-10T21:05:56Z","receivedAt":"2005-10-10T21:05:56Z","isPatch":false,"sender":{"key":"merlyn@stonehenge.com","avatar":"https://gravatar.com/avatar/dc528d210743ff0333e6213f9ee7b33b23f1b7bc1f3c5a8c2d819074ecd7ab19?d=mp&s=160"},"body":">>>>> \"H\" == H Peter Anvin writes:\n\nH> Sounds like an offer to send Mr. Schwartz some notes to work from. In\nH> my experience, sending notes to a good tech writer is about an order\nH> of magnitude less painful than writing polished documentation, so that\nH> should be easier.\n\nSince I'm benefitting from this project, I'd be happy to offer my services\nas time permits.\n\n-- \nRandal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095\n \nPerl/Unix/security consulting, Technical writing, Comedy, etc. etc.\nSee PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!\n"},{"id":"9936","messageId":"7v4q7p2h5v.fsf@assigned-by-dhcp.cox.net","threadId":"2058","inReplyTo":"86ek6tcdou.fsf@blue.stonehenge.com","subject":"Re: openbsd version?","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-10-10T21:31:08Z","receivedAt":"2005-10-10T21:31:08Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"merlyn@stonehenge.com (Randal L. Schwartz) writes:\n\n> Undocumented secret switches. Nice. No wonder\n> I couldn't find it.\n\nSorry. This is taken from the log message from the commit that\nintroduced the switch.\n\n git-branch -d : delete unused branch.\n \n The new flag '-d' lets you delete a branch. For safety, it does not\n lets you delete the branch you are currently on, nor a branch that\n has been fully merged into your current branch.\n \n The credit for the safety check idea goes to Daniel Barkalow.\n \n Signed-off-by: Junio C Hamano \n\nThere should be a document in Documentation/howto/ to describe\nhow to find the commit that introduced a particular feature.\nWhat I did to find the above is this:\n\n 1. Look at git-branch.sh and notice that there is this line:\n\n echo >&2 \"usage: $(basename $0)\"' [-d ] | [ [start-point]]\n\n Make an educated guess that this line, especially the\n \"[-d ]\" part, must have changed when the feature was\n added (that is, pre-modification file would not have had \"[-d\n ]\" in it, but post-modification file would).\n\n 2. Find such a change with pickaxe (-S):\n\n $ git whatchanged -S'[-d ]' git-branch.sh\n\nBy mentioning this, I do not mean to say that you could have\nfiguired this out yourself -- the above sequence is useful for\nsomebody who knows the code already to do archaeology; IOW you\nstill need to know what to look for, so the above procedure\nwould not have helped at all even if you knew about pickaxe.\n\n> Do these also flush any related object files? Or do I need git-fsck still?\n\nThe latter. I think there should be a general description in\nthe tutorial to advice the user to run git-fsck-objects every\nonce in a while, while mentioning that there is no need to do it\ntoo often -- disk space is cheap and the time you spend waiting\nfor fsck-objects to finish tends to be more expensive.\n"},{"id":"9934","messageId":"Pine.LNX.4.63.0510101703380.23242@iabervon.org","threadId":"2058","inReplyTo":"86y851aydl.fsf@blue.stonehenge.com","subject":"Re: openbsd version?","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2005-10-10T21:31:57Z","receivedAt":"2005-10-10T21:31:57Z","isPatch":false,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"On Mon, 10 Oct 2005, Randal L. Schwartz wrote:\n\n> >>>>> \"Johannes\" == Johannes Schindelin writes:\n> \n> >> Undocumented secret switches. Nice. No wonder\n> >> I couldn't find it.\n> \n> Johannes> Maybe he who found the documentation lacking is going to fix \n> Johannes> it?\n> \n> I'd be happy to do that. But as a tech writer, I know that it's\n> insane to not work at least from an implementor's rough draft, to at\n> least understand the intent of a mechanism, if not the precise design.\n> There's no implementor's rough draft here, so I can't help.\n\nThe mailing list thread on the subject is at:\n\n http://www.gelato.unsw.edu.au/archives/git/0509/8902.html\n\n(That's the middle of the thread, when the patch was actually written. \nThere's discussion before and after if you need more info.)\n\nYou can actually get a pretty good explanation of features, once you know \nthey exist at all, by looking for the discussion on the list. This tends \nto at least give you the person who did the patch explaining how to use it \nto the person who wanted the feature. And it'll also tell you who the \nimplementor was, so you can bug the right person directly. :)\n\nWhat does get written about a feature generall ends up in the commit \nmessage for the commit that adds it, so that's another good place to look. \n(In this case, it's missing a \"not\" and description of an option, so it's \nquite rough as a draft.)\n\nIn this case:\n\n \"git branch -d \" deletes a branch with that name; but it checks \nthat you're not on that branch, and it checks that that branch doesn't \nhave any commits which aren't merged into the current branch.\n \"git branch -D \" deletes a branch, and skips the second check.\n\n\t-Daniel\n*This .sig left intentionally blank*\n"},{"id":"9938","messageId":"7vzmph1225.fsf@assigned-by-dhcp.cox.net","threadId":"2058","inReplyTo":"20051010210007.GJ8383MdfPADPa@greensroom.kotnet.org","subject":"Re: openbsd version?","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-10-10T21:42:42Z","receivedAt":"2005-10-10T21:42:42Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Sven Verdoolaege writes:\n\n> I think you mean \n>\n> $ git-update-ref refs/heads/mybranch mybranch^\n\nOf course you are right. Thanks.\n"},{"id":"10057","messageId":"7vpsq9504x.fsf@assigned-by-dhcp.cox.net","threadId":"2058","inReplyTo":"7vzmph1225.fsf@assigned-by-dhcp.cox.net","subject":"Re: openbsd version?","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-10-13T07:47:26Z","receivedAt":"2005-10-13T07:47:26Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Junio C Hamano writes:\n\n> Sven Verdoolaege writes:\n>\n>> I think you mean \n>>\n>> $ git-update-ref refs/heads/mybranch mybranch^\n>\n> Of course you are right. Thanks.\n\nAnd I am an idiot. I did that myself again, and ended up\nwasting 30 minutes or so, scratching my head.\n\nMaybe there should be a safety measure built into git-update-ref\nthat says single-level name (i.e. not starting with refs/) gets\nwarning unless all uppercase or something silly like that to\nprotect idiots like myself. Hmmm.\n"},{"id":"10059","messageId":"20051013082928.GE8383MdfPADPa@greensroom.kotnet.org","threadId":"2058","inReplyTo":"7vpsq9504x.fsf@assigned-by-dhcp.cox.net","subject":"Re: openbsd version?","fromName":"Sven Verdoolaege","fromEmail":"skimo@kotnet.org","sentAt":"2005-10-13T08:29:28Z","receivedAt":"2005-10-13T08:29:28Z","isPatch":false,"sender":{"key":"skimo@kotnet.org","avatar":null},"body":"On Thu, Oct 13, 2005 at 12:47:26AM -0700, Junio C Hamano wrote:\n> Maybe there should be a safety measure built into git-update-ref\n> that says single-level name (i.e. not starting with refs/) gets\n> warning unless all uppercase or something silly like that to\n> protect idiots like myself. Hmmm.\n\nHow about checking whether the name also exists with a certain\nprefix instead ?\nOtherwise you'll also disallow updating ORIG_HEAD and stuff.\n\nskimo\n"}]}