# Development

**URL:** https://discourse.pijul.org/c/development/7.md?page=1

[Latest](https://discourse.pijul.org/latest.md) · [Categories](https://discourse.pijul.org/categories.md)

**Page:** 2

---

## [Building pijul for target x86\_64-pc-windows-msvc with vcpkg](https://discourse.pijul.org/t/building-pijul-for-target-x86-64-pc-windows-msvc-with-vcpkg/497)

<div class="topic-metadata">

**Author:** [@o01eg](https://discourse.pijul.org/u/o01eg)\
**Replies:** 5\
**Last updated:** [December 15, 2020, 10:21pm UTC](https://discourse.pijul.org/t/building-pijul-for-target-x86-64-pc-windows-msvc-with-vcpkg/497 "2020-12-15T22:21:49Z")

</div>

vcpkg dropped support for MSVC 2017 and requires MSVC 2019. Packages required to install are llvm\[clang\], nettle, openssl, libsodium. I set environments: set VCPKGRS\_DYNAMIC=1 set SODIUM\_LIB\_DIR=%VCPKG\_ROOT%\\installed\\…

---

## [Tags, Channels, and Remotes](https://discourse.pijul.org/t/tags-channels-and-remotes/668)

<div class="topic-metadata">

**Author:** [@Skia](https://discourse.pijul.org/u/Skia)\
**Replies:** 2\
**Last updated:** [December 11, 2020, 5:47am UTC](https://discourse.pijul.org/t/tags-channels-and-remotes/668 "2020-12-11T05:47:02Z")

</div>

Looking in the Pijul source code, it appears that “pijul record --tag” does not currently do any thing different from “pijul record” as the boolean flag “tag” is never checked for the the record command’s file. So, Piju…

---

## [Git Attributes Filter Equivalent](https://discourse.pijul.org/t/git-attributes-filter-equivalent/628)

<div class="topic-metadata">

**Author:** [@theduke](https://discourse.pijul.org/u/theduke)\
**Replies:** 1\
**Last updated:** [November 27, 2020, 5:02pm UTC](https://discourse.pijul.org/t/git-attributes-filter-equivalent/628 "2020-11-27T17:02:35Z")

</div>

Git provides a mechanism to modify file contents before they are checked out or comitted. This is very useful for tools like git-crypt, which transparently de/encrypt files in the repo (when specified in a .gitattribute…

---

## [1.0.0-alpha.3 Merging](https://discourse.pijul.org/t/1-0-0-alpha-3-merging/605)

<div class="topic-metadata">

**Author:** [@qrpnxz](https://discourse.pijul.org/u/qrpnxz)\
**Replies:** 14\
**Last updated:** [November 17, 2020, 5:02pm UTC](https://discourse.pijul.org/t/1-0-0-alpha-3-merging/605 "2020-11-17T17:02:29Z")

</div>

Merging is the bread and butter of distributed source control, so I want to get this straightened out in Pijul. Someone from hackernews posed the following scenario: I’m comparing git merge to adding a patch to a set …

---

## [Calling branches "branches" is misleading](https://discourse.pijul.org/t/calling-branches-branches-is-misleading/276)

<div class="topic-metadata">

**Author:** [@tae](https://discourse.pijul.org/u/tae)\
**Replies:** 20\
**Last updated:** [October 5, 2020, 10:26pm UTC](https://discourse.pijul.org/t/calling-branches-branches-is-misleading/276 "2020-10-05T22:26:30Z")

</div>

Coming from Git and Subversion this feature was difficult for me to understand. In those systems the analogy makes sense because you can draw the repository history as a bunch of timelines that are related to a main time…

---

## [Git compatibility](https://discourse.pijul.org/t/git-compatibility/192)

<div class="topic-metadata">

**Author:** [@EvqQChOcJ47gKp](https://discourse.pijul.org/u/EvqQChOcJ47gKp)\
**Replies:** 11\
**Last updated:** [September 26, 2020, 7:49am UTC](https://discourse.pijul.org/t/git-compatibility/192 "2020-09-26T07:49:36Z")

</div>

This project has to compete with git. Git is the de-facto standard, it is backed by such companies as GitHub and it will be very hard to compete. Git has lots of tooling around it. So I guess we need this project to be i…

---

## [Patch based version control](https://discourse.pijul.org/t/patch-based-version-control/513)

<div class="topic-metadata">

**Author:** [@joyously](https://discourse.pijul.org/u/joyously)\
**Replies:** 7\
**Last updated:** [July 23, 2020, 12:46am UTC](https://discourse.pijul.org/t/patch-based-version-control/513 "2020-07-23T00:46:44Z")

</div>

Continuing the discussion from Random Talks and Thoughts: I have never felt comfortable with Git. I have used Bazaar, and I recently reread an article explaining how the history is shown differently in Git, Mercurial, …

---

## [Writing the patch description from an editor](https://discourse.pijul.org/t/writing-the-patch-description-from-an-editor/55)

<div class="topic-metadata">

**Author:** [@lthms](https://discourse.pijul.org/u/lthms)\
**Replies:** 11\
**Last updated:** [May 10, 2020, 3:59pm UTC](https://discourse.pijul.org/t/writing-the-patch-description-from-an-editor/55 "2020-05-10T15:59:35Z")

</div>

Hi everybody. One of the latest “key feature” pijul still lacks from my point of view is the hability to write the patch description (that is the patch name and as much as text as you want then to give some context) wit…

---

## [Base 58 ⇒ Base 32](https://discourse.pijul.org/t/base-58-base-32/352)

<div class="topic-metadata">

**Author:** [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Replies:** 6\
**Last updated:** [January 9, 2020, 6:50pm UTC](https://discourse.pijul.org/t/base-58-base-32/352 "2020-01-09T18:50:17Z")

</div>

I’m in the process of changing the encoding of hashes from base58 to base32. The main reason to do this is to be able to use unique prefixes of hashes as shorthands in all commands. Also, the internal identifiers will th…

---

## [Random Talks and Thoughts](https://discourse.pijul.org/t/random-talks-and-thoughts/29)

<div class="topic-metadata">

**Author:** [@lthms](https://discourse.pijul.org/u/lthms)\
**Replies:** 19\
**Last updated:** [December 24, 2019, 10:34am UTC](https://discourse.pijul.org/t/random-talks-and-thoughts/29 "2019-12-24T10:34:01Z")

</div>

If you want to share something with the pijul contributors, yet you don' feel it deserves its own thread, here is the perfect place. The main idea is to exchange random thoughts or ideas in an informal way. For instanc…

---

## [Development plans](https://discourse.pijul.org/t/development-plans/401)

<div class="topic-metadata">

**Author:** [@lthms](https://discourse.pijul.org/u/lthms)\
**Replies:** 0\
**Last updated:** [August 22, 2019, 6:11am UTC](https://discourse.pijul.org/t/development-plans/401 "2019-08-22T06:11:29Z")

</div>

Hi, I have some spare time nowadays I would love to spend hacking pijul again. I saw not much happened for a few months. AFAIK @pmeunier has started to rewrite libpijul, so I guess I should concentrate on pijul cli. In…

---

## [Pijul is super slow when compared to git](https://discourse.pijul.org/t/pijul-is-super-slow-when-compared-to-git/395)

<div class="topic-metadata">

**Author:** [@gnzlbg](https://discourse.pijul.org/u/gnzlbg)\
**Replies:** 2\
**Last updated:** [August 19, 2019, 12:38pm UTC](https://discourse.pijul.org/t/pijul-is-super-slow-when-compared-to-git/395 "2019-08-19T12:38:46Z")

</div>

To reproduce: git clone https://github.com/openbsd/src.git --depth=1 rm -rf src/.git pijul init time pijul add --recursive src 6.94 real 4.05 user 2.72 sys $ time pijul record -am 'src' Recorded patch Aw…

---

## [Bug when importing LLVM into a Pijul repository](https://discourse.pijul.org/t/bug-when-importing-llvm-into-a-pijul-repository/393)

<div class="topic-metadata">

**Author:** [@gnzlbg](https://discourse.pijul.org/u/gnzlbg)\
**Replies:** 0\
**Last updated:** [August 12, 2019, 1:57pm UTC](https://discourse.pijul.org/t/bug-when-importing-llvm-into-a-pijul-repository/393 "2019-08-12T13:57:15Z")

</div>

There is a bug when importing the LLVM repository into a Pijul repository. To reproduce: git clone https://github.com/llvm/llvm-project.git --depth=1 pijul init pijul add --recursive llvm-project error: No such file or …

---

## [Pijul Bug with Unrecording?](https://discourse.pijul.org/t/pijul-bug-with-unrecording/361)

<div class="topic-metadata">

**Author:** [@krixano](https://discourse.pijul.org/u/krixano)\
**Replies:** 2\
**Last updated:** [May 26, 2019, 7:41am UTC](https://discourse.pijul.org/t/pijul-bug-with-unrecording/361 "2019-05-26T07:41:58Z")

</div>

I was going to post this to pijul’s nest repo, but looks like I can’t (see my other recent topic). A friend of mine had this bug with pijul. I don’t know exactly everything that happened, but I’ll give what I remember h…

---

## [Any plans to make tags first-class things?](https://discourse.pijul.org/t/any-plans-to-make-tags-first-class-things/335)

<div class="topic-metadata">

**Author:** [@kyegupov](https://discourse.pijul.org/u/kyegupov)\
**Replies:** 3\
**Last updated:** [May 12, 2019, 6:11pm UTC](https://discourse.pijul.org/t/any-plans-to-make-tags-first-class-things/335 "2019-05-12T18:11:16Z")

</div>

I’m a professional developer. I think in terms of delivering software and maintaining it. From that perspective, Pijul is a non-starter for me, because when I look at the repo and see just a long tower of patches (which…

---

## [Building a git-ssb like remote for ssb](https://discourse.pijul.org/t/building-a-git-ssb-like-remote-for-ssb/310)

<div class="topic-metadata">

**Author:** [@peacememories](https://discourse.pijul.org/u/peacememories)\
**Replies:** 0\
**Last updated:** [April 4, 2019, 2:37pm UTC](https://discourse.pijul.org/t/building-a-git-ssb-like-remote-for-ssb/310 "2019-04-04T14:37:58Z")

</div>

Hi, I’m very interested in Pijul as an alternative to Git. I’m also very interested in peer-to-peer systems, like Secure Scuttlebutt, and while I appreciate Pijul Nest a lot, I would love for a system like git-ssb to exi…

---

## [Using rustfmt systemically](https://discourse.pijul.org/t/using-rustfmt-systemically/211)

<div class="topic-metadata">

**Author:** [@lthms](https://discourse.pijul.org/u/lthms)\
**Replies:** 29\
**Last updated:** [March 14, 2019, 12:14pm UTC](https://discourse.pijul.org/t/using-rustfmt-systemically/211 "2019-03-14T12:14:13Z")

</div>

I’ve seen @pmeunier and @flobec creating “rustfmt patches” from times to times. I wonder if we shouldn’t make one last one, then using it systemically before recording any patches. This way, we will have a more consiste…

---

## [Ask before proceeding when unrecording a patch with dependencies](https://discourse.pijul.org/t/ask-before-proceeding-when-unrecording-a-patch-with-dependencies/277)

<div class="topic-metadata">

**Author:** [@tae](https://discourse.pijul.org/u/tae)\
**Replies:** 8\
**Last updated:** [February 23, 2019, 11:27pm UTC](https://discourse.pijul.org/t/ask-before-proceeding-when-unrecording-a-patch-with-dependencies/277 "2019-02-23T23:27:45Z")

</div>

Playing around I realized that if I unrecord a patch with dependencies the dependencies are unrecorded as well. That’s expected but I think it something people won’t have in mind while working so it would be nice if Th…

---

## [\[SOLVED\] KeyError fix](https://discourse.pijul.org/t/solved-keyerror-fix/265)

<div class="topic-metadata">

**Author:** [@az8](https://discourse.pijul.org/u/az8)\
**Replies:** 2\
**Last updated:** [February 23, 2019, 11:20pm UTC](https://discourse.pijul.org/t/solved-keyerror-fix/265 "2019-02-23T23:20:51Z")

</div>

Having complained here about a CouldNotReadKey bug over a year ago I finally found the time to dive in and figure out what was going wrong. My server has three keys. rsa , ecdsa and ed25519 . When connecting for the fir…

---

## [Bad performance](https://discourse.pijul.org/t/bad-performance/134)

<div class="topic-metadata">

**Author:** [@yory](https://discourse.pijul.org/u/yory)\
**Replies:** 16\
**Last updated:** [December 11, 2018, 8:01pm UTC](https://discourse.pijul.org/t/bad-performance/134 "2018-12-11T20:01:55Z")

</div>

Hello! I’m a new user. While trying pijul to replace git for my personal projects, I was quite surprised that I hit some pretty strong performance issues. My use cases were: a repo with a single 4MB file a repo with …

---

## [Patching patches](https://discourse.pijul.org/t/patching-patches/212)

<div class="topic-metadata">

**Author:** [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Replies:** 19\
**Last updated:** [September 12, 2018, 7:06pm UTC](https://discourse.pijul.org/t/patching-patches/212 "2018-09-12T19:06:27Z")

</div>

Here is a feature that someone suggested to me today: patches that operate on other patches rather than on the direct text. One potential implementation (but I have other ideas as well) could be to represent some patche…

---

## [A composable pijul user interface? (brainstorm)](https://discourse.pijul.org/t/a-composable-pijul-user-interface-brainstorm/100)

<div class="topic-metadata">

**Author:** [@pointfree](https://discourse.pijul.org/u/pointfree)\
**Replies:** 20\
**Last updated:** [May 2, 2018, 6:46am UTC](https://discourse.pijul.org/t/a-composable-pijul-user-interface-brainstorm/100 "2018-05-02T06:46:47Z")

</div>

See the discussion here: https://nest.pijul.com/pijul\_org/pijul/discussions/60

---

## [Benchmarking pijul](https://discourse.pijul.org/t/benchmarking-pijul/201)

<div class="topic-metadata">

**Author:** [@lthms](https://discourse.pijul.org/u/lthms)\
**Replies:** 1\
**Last updated:** [April 25, 2018, 8:33am UTC](https://discourse.pijul.org/t/benchmarking-pijul/201 "2018-04-25T08:33:30Z")

</div>

pijul theoretical performance has been advertised since as far as I can recall. Now that pijul-0.10.1 has landed, I believe it is a good time for caring about how our changes affect them. Therefore, in addition to the aw…

---

## [Last adjustments before Pijul 0.10](https://discourse.pijul.org/t/last-adjustments-before-pijul-0-10/191)

<div class="topic-metadata">

**Author:** [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Replies:** 2\
**Last updated:** [April 20, 2018, 9:30pm UTC](https://discourse.pijul.org/t/last-adjustments-before-pijul-0-10/191 "2018-04-20T21:30:55Z")

</div>

I’m about to release Pijul 0.10, but before I can do so, we need to decide what to do about liner/rustyline/… which apparently have been stalled for about a year. After evaluating a number of alternatives, which involve…

---

## [Semantics of "missing contexts" conflicts](https://discourse.pijul.org/t/semantics-of-missing-contexts-conflicts/171)

<div class="topic-metadata">

**Author:** [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Replies:** 6\
**Last updated:** [March 13, 2018, 10:03am UTC](https://discourse.pijul.org/t/semantics-of-missing-contexts-conflicts/171 "2018-03-13T10:03:09Z")

</div>

Here’s a question related to my current effort to iron out the remaining bugs/unimplemented things in libpijul: how should we represent conflicts arising from missing contexts? A missing context is the situation that ar…

---

## [Lots of conflicts](https://discourse.pijul.org/t/lots-of-conflicts/139)

<div class="topic-metadata">

**Author:** [@joeneeman](https://discourse.pijul.org/u/joeneeman)\
**Replies:** 6\
**Last updated:** [February 20, 2018, 11:33am UTC](https://discourse.pijul.org/t/lots-of-conflicts/139 "2018-02-20T11:33:06Z")

</div>

A fresh checkout of pijul doesn’t build, because it’s full of conflicts. I installed a fresh version of pijul with cargo install pijul and then I closed the repository with pijul clone https://nest.pijul.com/pijul\_org/p…

---

## [Getting ready for 0.9](https://discourse.pijul.org/t/getting-ready-for-0-9/125)

<div class="topic-metadata">

**Author:** [@flobec](https://discourse.pijul.org/u/flobec)\
**Replies:** 3\
**Last updated:** [January 11, 2018, 9:09am UTC](https://discourse.pijul.org/t/getting-ready-for-0-9/125 "2018-01-11T09:09:28Z")

</div>

Happy new year fellow pijulers, do we have a planning for the release of 0.9. In particular, given that we should undergo a format change, we need to: release a 0.9 tarball switch the nest to pijul-0.9 state what the …

---

## [Prepare the release of pijul-0.8](https://discourse.pijul.org/t/prepare-the-release-of-pijul-0-8/73)

<div class="topic-metadata">

**Author:** [@lthms](https://discourse.pijul.org/u/lthms)\
**Replies:** 9\
**Last updated:** [December 30, 2017, 5:53am UTC](https://discourse.pijul.org/t/prepare-the-release-of-pijul-0-8/73 "2017-12-30T05:53:00Z")

</div>

Hi everyone. I think the current state of pijul is pretty interesting and we should release it. Here is the current ChangeLog. What do you think? ChangeLog Features Pijul can now deal with cyclic conflicts when unreco…

---

## [Heads-up: recent bugs with conflicts and with the Nest](https://discourse.pijul.org/t/heads-up-recent-bugs-with-conflicts-and-with-the-nest/71)

<div class="topic-metadata">

**Author:** [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Replies:** 5\
**Last updated:** [August 31, 2017, 9:02pm UTC](https://discourse.pijul.org/t/heads-up-recent-bugs-with-conflicts-and-with-the-nest/71 "2017-08-31T21:02:50Z")

</div>

Hi all, I just wanted to give you a quick heads-up about things I’m currently doing in Pijul: The Nest was previously using my own hack to do HTTP, it’s now using Tokio. I originally wrote it because Hyper had no Tok…

---

## [Request for comments: Listing files with conflicts in \`pijul status\`](https://discourse.pijul.org/t/request-for-comments-listing-files-with-conflicts-in-pijul-status/49)

<div class="topic-metadata">

**Author:** [@laumann](https://discourse.pijul.org/u/laumann)\
**Replies:** 13\
**Last updated:** [August 26, 2017, 2:54pm UTC](https://discourse.pijul.org/t/request-for-comments-listing-files-with-conflicts-in-pijul-status/49 "2017-08-26T14:54:09Z")

</div>

One of the really cool features of Pijul (IMO) is a good internal representation of conflicts. But I find myself searching for conflicts after a pull by grepping for something like \>\>\>\>\>\> to find files with conflicts. @…

[Previous page](https://discourse.pijul.org/c/development/7.md)

[Next page](https://discourse.pijul.org/c/development/7.md?page=2)
